When you are analyzing your software system development project you need to adequately set the stage for your Design Phase One way to do this is to have an Analysis Phase documentation package that can guide your design efforts and delineate how your software system is to function What specifications models and delineations would you include in this analysis design documentation package The analysis phase needs to document all known and potential variables related to the project A well created analysis documentation should include total cost estimates ROI time frames contain different design diagrams and the physical models available to the project The idea behind the analysis phase is to gain a strong understanding of the process needed to bring about a successful project I would also state that its important to know for WHO you are preparing the analysis phase documentation Project managers and shareholders require special documentation that generalizes the project s flow while engineers need documentation that presents design patterns frameworks packages subpackages and subsubpackages Although the final presentation and accompanying diagrams might differ between the two groups a few essential concerns will appear in both presentations The four basic models described in our eBook Software Engineering are use case model class model data flow model and state model Each of these models will need developing According to the posts made by our professor he delineations consist of two models logical and physical Each of these models cascade into ever increasing detail The logical model describe the processes and procedures for the project The physical model depicts the different hardware software databases and system interfaces needed for the project An analysis documentation containing all these elements will provide a wonderful framework to present to clients managers and engineers
View Full Document
Unlocking...