System Requirements Specification Document, Essays (university) of System Analysis and Design

System requirements specification Tamp-let

Typology: Essays (university)

2016/2017

Uploaded on 11/20/2017

tinashe-mudzimu
tinashe-mudzimu 🇿🇼

2 documents

1 / 2

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
1 Introduction
1.1 Purpose
This document in narrates in detail the Requirements Specification the Enhanced Personnel
Administration and Management System (EPAMS). It expounds the scope of EPAMS system, both
functional and non-functional requirements for the software, design constraints and system interfaces.
1.2 Scope
the Enhanced Personnel Administration and Management System addresses the need for fully
encompassing electronic Human resources management application which is exhaustive in operation.
It provides almost all personnel administration functions from shortlisting up to termination of
contract with a full captured and retrievable history. The system is universally applicable through the
cooperate divide.
This document only describes required functionality of EPAMS, not the functionality of external
systems like data storage, change management or version control systems. This document does not
divide the EPAMS into subsystems; it describes only requirements for the whole system functionality
which is defined in the use case model.
1.2.1 Use Case Model
To define and organize the functional requirements of the EPAMS, this document uses as a basis the
use case model. The use case model consists of all actors of the system and all the various use cases
by which the actor interact with the system and describes the total functional behaviour of the system.
1.3 Definitions, Acronyms, and Abbreviations.
Provide the definitions of all terms, acronyms, and abbreviations required to properly interpret the
SRS. This information may be provided by reference to one or more appendices in the SRS or by
reference to documents. This information may be provided by reference to an Appendix.
1.4 References
In this subsection:
(1) Provide a complete list of all documents referenced elsewhere in the SRS
(2) Identify each document by title, report number (if applicable), date, and
publishing organization
3. Specify the sources from which the references can be obtained.
This information can be provided by reference to an appendix or to another document. If your
application uses specific protocols or RFC’s, then reference them here so designers know where to
find them.
1.5 Overview
In this subsection:
1. Describe what the rest of the SRS contains
2. Explain how the SRS is organized
pf2

Partial preview of the text

Download System Requirements Specification Document and more Essays (university) System Analysis and Design in PDF only on Docsity!

1 Introduction 1.1 Purpose This document in narrates in detail the Requirements Specification the Enhanced Personnel Administration and Management System (EPAMS). It expounds the scope of EPAMS system, both functional and non-functional requirements for the software, design constraints and system interfaces. 1.2 Scope the Enhanced Personnel Administration and Management System addresses the need for fully encompassing electronic Human resources management application which is exhaustive in operation. It provides almost all personnel administration functions from shortlisting up to termination of contract with a full captured and retrievable history. The system is universally applicable through the cooperate divide.

This document only describes required functionality of EPAMS, not the functionality of external systems like data storage, change management or version control systems. This document does not divide the EPAMS into subsystems; it describes only requirements for the whole system functionality which is defined in the use case model. 1.2.1 Use Case Model To define and organize the functional requirements of the EPAMS, this document uses as a basis the use case model. The use case model consists of all actors of the system and all the various use cases by which the actor interact with the system and describes the total functional behaviour of the system.

1.3 Definitions, Acronyms, and Abbreviations.

Provide the definitions of all terms, acronyms, and abbreviations required to properly interpret the SRS. This information may be provided by reference to one or more appendices in the SRS or by reference to documents. This information may be provided by reference to an Appendix.

1.4 References

In this subsection:

(1) Provide a complete list of all documents referenced elsewhere in the SRS

(2) Identify each document by title, report number (if applicable), date, and

publishing organization

3. Specify the sources from which the references can be obtained.

This information can be provided by reference to an appendix or to another document. If your application uses specific protocols or RFC’s, then reference them here so designers know where to find them.

1.5 Overview

In this subsection:

  1. Describe what the rest of the SRS contains
  2. Explain how the SRS is organized

Don’t rehash the table of contents here. Point people to the parts of the document they are most concerned with. Customers/potential users care about section 2, developers care about section 3.

2 Market analysis