Drafting of Technical Requirements for Ombudsman Software for Case Processing Development. The scope of this project is to gather technical requirements by using requirements gathering techniques for developing of Ombudsman software for case processing. The gathered technical requirements shall consist of:
– Functional Requirements
– Non-Functional Requirements
| Client: | OSCE | | Origin of funding: | OSCE | | Date: | February 2008 – May 2008 | | Partners: | None | | Types of Services Provided: | The completed, gathered requirements will:
– Define the scope of the project
– Define functionalities of the system described also with use cases
– Define Business Processes – this should cover all business processes (which is a set of coordinated tasks that achieve a business goal) with their rules and constraints that are on-going in the Ombudsman Offices, i.e. the case processing activities from registering of a case to starting an investigation on it
– Defining of all actors in the processes at the Ombudsman offices and users of the information system
– Describe Hardware Infrastructure at the Ombudsman offices (including available servers, workstations and system software)
– Define Security Requirements for implementation of open and well established standards in security and privacy
The technical documentation for development of software for case processing shall include, based on UML 2.0 notation:
– Requirements catalogue
– Business rules and constraints - a view of all business rules and constraints within the activities of case processing at the Ombudsman offices
– Functional requirements view - Functional requirements shall be covered with use-cases and appropriate diagrams
– Static structural view - The quintessential object-oriented step in analysis or gathering requirements is the decomposition of a domain of interest into individual conceptual classes or objects — the things we are aware of. A domain model is a visual representation of conceptual classes or real-world objects in a domain of interest
– Dynamic behavior view - Dynamic Behavioral model describes the internal dynamic aspects of the information system that supports the business processes in the Ombudsman Offices. During the analysis phase the behavioral models describe what the internal logic of the processes is without specifying how the processes are to be implemented. | |
