• Guidance
• Grading
• List of Requirements
• Test Case description
• References

Guidance

The software shoud be developed according to variant, assinged by teacher.

1. Make an Excel file with input information according to your task.
2. Download the Project Charter short template and fill the Project Charter according notes in the file.
3. Make a software specification as a Requirements list (according to standard ISO/IEC 29110, description is in section List of Requirements). You should use knowledge obtained in Unit 3. 
4. Define actors and use cases of software. Make a Use Case Diagram. You should use knowledge obtained in Unit 4 and skills acquired in Practice 8 and 9.
5. Make a user interface sketch using any tool for UI design (e.g. Balsamiq or draw.io).You should use knowledge obtained in Unit 5. 
6. Define program classes for use case realization. Make a Class Diagrams to show program structure. You should use knowledge obtained in Unit 3.
7.  Define test cases (description is in section Test Case description). to check software compliance to use cases.
8. 8. Implement design solution as a software in Visual Studio on C# programing language. Make user and installation manuals. You should use knowledge obtained in Unit 4 and skills acquired in Practice 8 and 9.
9. 9. Test software according developed on step 6 test cases.
10. 10. Complete the project report using some text redactor (for example, MS Word), save it and send it and software files to the teacher.

 

Grading

You can get the maximum 100 points to your score. 

To gain minimum mark for execution of course project you must complete software design project (p.1-7 of guidence) and send to teacher comleted paper work (must contain sections Introduction, Task statement, Software Project and Appendix A).

 

List of Requirements

Table 1 - List of requirements according to standard ISO/IEC 29110 [1]

ID Requirement text Status Priority Verification method Notes

where

 ID - project-unique identifier which allows the unambiguous referencing of a requirement throughout the project.

A proposed identifier schema is as follows: ABCXYZ_9999 where: 

ABC identifies the requirement level, as follows: 
STK: Stakeholder Requirement 
SYS: System Requirement 
SEL: System Element Requirement or, alternately 
SRS: Software Requirement 
HLR: High-level Software Requirement (DO-178B/C) 
LLR: Low-Level Software Requirement (DO-178B/C) 
HRS: Hardware Requirement 
XYZ identifies the project, system or system element 
9999: A sequence number serializing related requirements 

Examples: 
  STKMCS_0023: Stakeholder Requirement #23 for the Mobile Communications System (MCS) 
  SYSMCS-0970: System Requirement #970 for the Mobile Communications System (MCS) 
  SELNRU-2325: System Element Requirements #2325 for the MCS Node Radio – UHF (NRU) 

Status - requirement status (Draft/Ready/Reviewed/Approved/Released)

Verification Method - Test (T)/Demonstration (D)/Inspection (I)/Analysis (A)

 

Test Case description

Table 2 - Test Case (TC) description

TC ID Description Actions Expected Results Status

References

1. ISO/IEC 29110-5 Systems and software engineering - Life cycle profiles for Very Small Entities, Deployment Package – Needs and System Requirements Definition v.2.0