ProCiv Project

Here you will find all the information to the Software Requirements project. The main idea is to support Civil Protection with a mobile application that can provide both push and pull functionalities related to the domain, the task for the teams will be to model the requirements for such project (please do not share the provided material).
 

Project Context

You will find all information related to the domain: what the goals of the Civil Protection are, how it operates, the needs in general. In the last part, you find some ideas and needs for implementation of a new system (slides 35-42): take into account that the needs for the overall system are at the pages 37-42, that is composed of different applications/sub-systems (e.g., one is the mobile application). [download]

Initial Elicitation

There is an initial document that collects requirements collected from the customer. However, it is mixing several aspects into requirements (mixing features with functional / non-functional requirements, constraints, design decisions, etc...) plus ambiguous parts (e.g. "constantly"). You can use this document as a starting point for requirements analysis by extracting relevant information and better structuring it. [download]

The following are some rough milestones for project delivery.

Step 1 (by 18.03.2019):

• Start with a simple document about the business requirements (does not need to include all seen during the lecture, just the major parts)
  
• add an initial statement about the project business vision
• Create a context diagram (or ecosystem map) for the project

Step 2 (by 01.04.2019)

• structure the requirements in the form suggested by IEEE Std 29148-2011  (note: you might mix with agile, more details during lecture)
• prioritized list of requirements: pick one method seen during lecture (AHP or planning poker) and provide the list of prioritized requirements

Step 3 (by 15.04.2019)

• Add representative use cases for the project
• Perform the initial CRC Analysis for part of the system
  

Step 4 (by 29.04.2019)

• add the Non-Functional Requirements (NFR) to the project according to what seen during the lectures, e.g. by following the standard ISO/IEC 9126 with the definition of precise set of metrics to measure the quality characteristics

Step 5 (by 13.05.2019)

• add the architectural representation of the system (you can add all the considerations about the way you would structure the system, according to non-functional (and functional) requirements. You can use the ADD method document as an example, but it does not need to be so detailed, the important is that you have NFRs, and indication how NFRs will be reflected in the architectural choices).
• Start refining/revising the overall requirements specification produced
  

Step 6 (for final presentation on 20.05.2019)

• Mock-ups / UI prototypes - can be useful to show how the application will look like.
• Revise the whole requirements specification, so that it follows indications from different standards we have seen during lecture.