

Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
System requirements specification Tamp-let
Typology: Essays (university)
1 / 2
This page cannot be seen from the preview
Don't miss anything!


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.
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.
In this subsection:
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.
In this subsection:
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.