1. Introduction to The system: describe the need for the system and describe briefly the system's functions. 2. Glossary: This should define the technical terms used in the document. 3. Purpose of the system: pills in Long 4. Methodology: Choose the appropriate methodology to concept such a system: Waterfall, Incremental, reuse oriented, Spiral, Agile, ... 5. User requirements definition Describe the services provided for the user. The nonfunctional system requirements should also be described in this section. This description may use natural language, diagrams, or other notations that are understandable to customers. 6. System Requirement specification This should describe the functional and nonfunctional requirements in more detail. If necessary, further detail may also be added to the nonfunctional requirements. Interfaces to other systems may be defined 7. System Models Uses Cases Diagrams Class Diagram Sequence diagram: you take 2 or 3 uses cases and you draw the appropriate sequences diagrams. Activity diagram 8. Index: If it exist. Plan of Software Engineering Presentation . 1. Introduction to The system: describe the need for the system and describe briefly the system's functions. 2. Glossary: This should define the technical terms used in the document. 3. Purpose of the system: pills je well 4. Methodology: Choose the appropriate methodology to concept such a system: Waterfall, Incremental, reuse oriented, Spiral, Agile, ... 5. User requirements definition Describe the services provided for the user. The nonfunctional system requirements should also be described in this section. This description may use natural language, diagrams, or other notations that are understandable to customers. 6. System Requirement specification This should describe the functional and nonfunctional requirements in more detail. If necessary, further detail may also be added to the nonfunctional requirements. Interfaces to other systems may be defined 7. System Models Uses Cases Diagrams Class Diagram Sequence diagram: you take 2 or 3 uses cases and you draw the appropriate sequences diagrams. Activity diagram 8. Index: If it exist. 1. Introduction to The system: describe the need for the system and describe briefly the system's functions. 2. Glossary: This should define the technical terms used in the document. 3. Purpose of the system: pills in Long 4. Methodology: Choose the appropriate methodology to concept such a system: Waterfall, Incremental, reuse oriented, Spiral, Agile, ... 5. User requirements definition Describe the services provided for the user. The nonfunctional system requirements should also be described in this section. This description may use natural language, diagrams, or other notations that are understandable to customers. 6. System Requirement specification This should describe the functional and nonfunctional requirements in more detail. If necessary, further detail may also be added to the nonfunctional requirements. Interfaces to other systems may be defined 7. System Models Uses Cases Diagrams Class Diagram Sequence diagram: you take 2 or 3 uses cases and you draw the appropriate sequences diagrams. Activity diagram 8. Index: If it exist. Plan of Software Engineering Presentation . 1. Introduction to The system: describe the need for the system and describe briefly the system's functions. 2. Glossary: This should define the technical terms used in the document. 3. Purpose of the system: pills je well 4. Methodology: Choose the appropriate methodology to concept such a system: Waterfall, Incremental, reuse oriented, Spiral, Agile, ... 5. User requirements definition Describe the services provided for the user. The nonfunctional system requirements should also be described in this section. This description may use natural language, diagrams, or other notations that are understandable to customers. 6. System Requirement specification This should describe the functional and nonfunctional requirements in more detail. If necessary, further detail may also be added to the nonfunctional requirements. Interfaces to other systems may be defined 7. System Models Uses Cases Diagrams Class Diagram Sequence diagram: you take 2 or 3 uses cases and you draw the appropriate sequences diagrams. Activity diagram 8. Index: If it exist
