The aim of this project is to simulate a proper systems design, will need to make the necessary assumptionsto identify the design requirements
12:Details about the design problem as understood by the design team
Scope
Identifying stakeholders
Identifying key functional and non-functional requirements
Identifying an estimate of the project
Identifying a time schedule for the project
13. Constraints and limitations on the design
14. Assumptions made
f. Designing the software systems using various types of models as follows: An entity relationship diagram
g. A matching class diagram
h. A complete set of use case diagrams
i. Activity diagrams for use cases related to establishing new projects
j. System sequence diagrams for the diagrams in d.
Each Model should be introduced and point out the aim of the model and how you design it. Include a brief explanation and description for each model.
Implementation and deployment of the Solution
The purpose of the Stakeholder Needs and Requirements definition activities are to elicit a set of clear and concise needs related to a new or changed mission for an enterprise (see mission analysis (MA) for information relevant to identifying and defining the mission or operation), and to transform these stakeholder needs into verifiable stakeholder requirements.
Identifying Stakeholders:
Stakeholders of a SoI may vary throughout the life cycle. Thus, in order to get a complete set of needs and subsequent requirements, it is important to consider all stages of the life cycle model when identifying the stakeholders or classes of stakeholders.
Identifying Stakeholder Requirements:
Stakeholder needs are transformed into a formal set of stakeholder requirements, which are captured as models or documented as textual requirements in and output typically called a Stakeholder Requirement Specification (StRS), Stakeholder Requirement Document (StRD) or similar.
Comments
Leave a comment