Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
[Note: The following template is provided for use with the 7403ICT – eService Management. Text
enclosed in square brackets [] and shown in blue italics is included to provide guidance to students and
should be deleted before submitting your assignment.]
[Place your revision history in here. (i.e. Changes made by both members)
Your lecturer wants to see how you have been working on this document during the semester,
and who’s done what and when.]
Table of Contents
[Insert the Section headings and page numbers automatically here. DO NOT TYPE THEM
IN.)
Using MS Word:
Insert
Reference
Index & Tables
Table of Contents, & 2 levels.]
[Specify here the purpose of this System Requirements Specification and Analysis Document– why
has it been developed, to what system or subsystem does it refer.]
1.2 Scope
1.2.1 Document [What is the scope of this document. Who will use it and how will
it be used]
1.2.2 Project [What is the scope of the project. What will you deliver]
[This subsection provides the definitions of all terms, acronyms, and abbreviations required to
properly interpret the document
2. System Overview
[This section provides a DESCRIPTION in your own words of the proposed system. Reference should
be made to the system purpose and meeting organisational goals and objectives]
3. Scoping Models
[Provide a brief introduction to this section. This should include identification of ( a) the techniques
and tools used to analyse the system, and (b) the models presented in the following sections ]
4. System Requirements
[This section contains all system requirements to a level of detail sufficient to enable
designers to design a system to satisfy those requirements.]
4.1 Functional Requirements
[This section describes the software system requirements (what the system must do) for the
current system, and how it is represented.
4.2 Non Functional Requirements
[This Specification must also capture requirements that are not included in the specific
functional requirements, which are applicable to this system or subsystem. Make sure that
each requirement is clearly numbered.]
4.3 Constraints
[This section indicates any constraints on the system being built. Constraints represent
decisions that have been mandated and must be adhered to. Examples include software
process requirements (SDLC model), prescribed use of developmental tools, architectural
and/or design constraints, purchased components, and so on. EACH constraint must be
NUMBERED]