logo

ITC548 - System Analysis of Business - Report

   

Added on  2020-03-02

12 Pages2129 Words167 Views
Student detailsStudent nme

Question 1System analysis is the process of the business process of an organization in order to identify the goals and the main purpose of the business to create a system that will help achieve them in an efficient way (Satzinger, Jackson and Burd, 2012). System analysis can also be defined as the process of breaking down a system into components and studying how the components integrate and work together to form the complete system (Subramanian, 2000).Question 2System development life cycle (SDLC) is the process through which an information system is created from scratch up to when it’s finished. SDLC involves planning, creating, testing and deploying the information system. It’s also referred to as application development life cycle.Question 3UML DiagramDefinition Where Used in SDLC?Class DiagramA class diagram is a diagram that is used to show the static structure of asystem by showing the classes of a system, the attributes that define the classes, the relationships between the classes and the operations or methods belonging to the classes.This diagram is used in modelling of objected oriented systems to show the structure os a system by breaking it down into classes.Use Case DiagramA use case diagram is a diagram usedin system analysis to depict how different elements interact with a system.This diagram is used to show actors of a system and their intreactions with the systemActivity DiagramAn activity diagram is diagram used in system analysis to model computational processes of an information system and the organizational workflows of an organization.This diagram is sued to show the workflow of the systemArchitectural Configuration DiagramThis is a diagram used in system analysis to describe the architecture of a software system by showing groups of components making the system, their connections and how they interact.This diagram to show the behavior of a system by showing internal and external elements of the system

UML DiagramDefinition Where Used in SDLC?Design Class DiagramA design class diagram is a diagram used in software engineering to show classes making up a system and how they are interrelated. The interrelationships between the classes may include, association, inheritance or aggregation.This diagram is used to show the properties of a class and its relationships with other classesArchitectural Design DiagramAn architectural design diagram is a diagram used in system analysis to show the structure and the design ofa systemThis diagram is sued to givea conceptual view of the system’s architecture.QUESTION 4:Use cases as defined above is a diagram used to show how different elements interact with a system. The information provided by a list of format use case includes;The boundary of the system in relation to what surrounds it. This can be seen as the scope of the system in relation to the world around it.The actors who interact with the system through various roles.The use cases which depict what roles are played by which actor around and within the systemThe relationship that exists between the actors and the use cases and among the actors and the uses cases (Rouse, 2015)QUESTION 5ItemDefinition (complete thestatement...)Reference1A “Requirement” is: an expectation of a user for a certain system or simply a requirement is what the user expects the system to do.REQUIREMENTS ENGINEERING. (n.d.). Retrieved August 22, 2017, from http://www.sei.cmu.edu/productlines/frame_report/req_eng.htm2A “Functional Requirement” is: a a requirement that specifies what the system is supposed to do.Erikson, U. (2015, April 3). THE DIFFERENCE BETWEEN FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS. Retrieved August 23, 2017, from http://reqtest.com/requirements-blog/understanding-the-difference-between-functional-and-non-

functional-requirements/3A “Non-Functional Requirement” is: a requirement that specifies how the system is supposed to perform a specific function by showing how the system should behave and its limit onthe functionality.Erikson, U. (2015, April 3). THE DIFFERENCE BETWEEN FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS. Retrieved August 23, 2017, from http://reqtest.com/requirements-blog/understanding-the-difference-between-functional-and-non-functional-requirements/Question 6:The major problem with dealing with different types of stakeholders is conflicts where by stakeholders can conflict either on the functional or nonfunctional requirements of the project.The main reason for the conflict is that each stakeholder has a part to play in the development of the software thus different stakeholders may have conflicting interests over issues affecting the project, For example the project manager who is in charge of the whole project may disagree with the customer because of the popular rule of business that the customer is always right.Question 7The main themes to consider when interviewing stakeholders are;Traceability- each requirement must be traceable.Understandable- each requirement should be understandable.Unambiguous- each requirement said by the stakeholder should not be ambiguousConcise- each requirement should be concise and straight to the point.Feasible- each requirement by a stakeholder should be attainable.Question 8The use case diagram and the class diagram together drive the overall system development because when the use case is modelled and its done making sure that all the actors are not left out and that all the requirements are shown then the use case can be analyzed to form a system which is then broken down to a structure of individual classes. The classes are the objects that form the system and their methods, attributes give a conceptual view of the structure of the system thus the design can be gotten from the class diagram. With all the designs achieved from the class diagram then the implementation can be done based on the design and later testing can also be done by analyzing the class diagram.Question 9

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Software Development Life Cycle (SDLC) and System Analysis Process
|13
|1527
|469

Use Case Model Diagram (Logical Design Diagram) Assignment
|27
|5261
|344

Case Model Diagram
|26
|5411
|298

(Doc) UML Diagram Assignment
|42
|1048
|155

System Analysis and Design – Assignment
|18
|3126
|113

Desklib - Online Library for Study Material with Solved Assignments, Essays, Dissertations
|28
|5911
|302