IT425-1403A-01 : Systems Analysis, Design and Integration - Assignment Example

Systems Analysis, Design and Integration Systems Analysis, Design and Integration The overall layout of the system analysis process is correct. It starts well with the scope definition where the project plan is communicated, and the baseline scope negotiated. Problem analysis is then done to help understand the problem domain and analyze business processes involved in the system. The project then proceeds to requirement analysis where the system requirements are identified and expressed. The logical design is then made by the composition of the dataflow diagrams and use case diagrams.

The system is then tested and evaluated for approval by both the sponsors and the customers to ensure acceptability (INTEGRATION AND TEST PHASE). The project closes with the quality assurance plan that ensures efficient development and use of the resources. This is vital for the development of any system (Systems Development Life Cycle, 2014). However, the system design does not have the decision analysis phase where candidate solutions might have been identified, analyzed and the best solution implemented.

A data flow diagram is well-drawn as it disintegrates the system into smaller parts called processes that characterize the pizza system. Data also appropriately enters the system from an external environment. These data then flows between the processes undergoing processing and then finally the result is produced. The data flow diagram also provides a clear representation of the system. The model starts well with the overall picture of the pizza system and then continues to analyze each of the functional areas of interest.

The analysis is carried out to precise the level of details required. The student uses the top-down expansion to accomplish the analysis in the best way possible (“Data Flow Diagram Software”, 2014). A data flow diagram is also simple and straightforward (Kozar, 1997). The use case diagrams are also excellently constructed. At the initial step, all the top-level behavior have been identified. Details are then continually added to the use case by decomposing the use cases. The use cases are an actual depiction of the system functionality (Heywood).

The functional decomposition diagram also shows on a single page the functions of the system. From this diagram, it is simple to develop the models of the system. (Togaf-Modeling.org, 2013). Heat maps are also layered on top of the functional decomposition diagrams to show their scope and decisions. The diagrams are linked to other parts of the model to show how the applications support each other hence a comprehensive diagram. The sequence diagrams models the flow of logic within the system and shows the steps and the interaction between objects.

The diagram enables for the documentation and validation of the logic. It also rightly identifies the behavior of the system being modeled. The diagram shows how the system is used for example the diagram shows whether the customer has already made an order or not (Ambler, 2014). However, there are some issues that are not addressed in the system. The project fails to mention the type of the system development method implemented (Systems Development Life Cycle[, 2014). The tests and evaluation that fail the test are not mentioned as being migrated back to the development phase for reconsideration, and the successful components migrated for implementation.

ReferenceAmbler, S. W. (2014). UML 2 Sequence Diagrams: An Agile Introduction. Retrieved August 2, 2014, from Agile Modelling: http://www.agilemodeling.com/artifacts/sequenceDiagram.htmData Flow Diagram Software, Create data flow diagrams rapidly with free examples and templates. (2014). Retrieved August 2, 2014, from EdrawSof: http://www.edrawsoft.com/Data-Flow-Diagrams.phpHeywood, R. (n.d.). UML Use Case Diagrams: Tips and FAQ. Retrieved August 1, 2014, from UML Use Case Diagrams: Tips and FAQ: https://www.andrew.cmu.

edu/course/90- 754/umlucdfaq.htmlIntegration and test phase. (n.d.). Retrieved August 1, 2014, from http://www.justice.gov/jmd/irm/lifecycle/ch9.htmKozar, K. A. (1997). The Technique of Data Flow Diagramming. Retrieved August 2, 2014, from The Technique of Data Flow Diagramming: http://spot.colorado.edu/~kozar/DFDtechnique.htmlSystems Development Life Cycle[. (2014, June 5). Retrieved August 2, 2014, from Systems Analysis and Design/Introduction: http://en.wikibooks.org/wiki/Systems_Analysis_and_Design/IntroductionTogaf-Modeling.org. (2013, October 29).

Functional decomposition diagrams. Retrieved August 2, 2014, from Togaf-Modeling.org : http://www.togaf-modeling.org/models/business- architecture-menu/functional-decomposition-diagrams-menu.html