Professional Documents
Culture Documents
Specification Document
for
<client>
1. Introduction
1.1 Tujuan
1.3 Referensi
[1] Software Requirements Specification for <Project>.
http://www.ittelkom.ac.id/staf/kms/Slide kuliah dan tugas RPL/SRS template.doc
2. Overall Description
2.1 Product Perspective
This subsection of the SRS puts the product into perspective with other related
products or projects.
If the product is independent and totally self-contained, it should be stated here.
If the SRS defines a product that is a component of a larger system or project,
as frequently occurs, then this subsection should:
Describe the functions of each component of the larger system or project,
and identify interfaces
Identify the principle external interfaces of this software product.
A block diagram showing the major components of the larger system or
project, interconnections, and external interfaces can be very helpful.
Admin
Sub Admin
Bagian
Akademik User
Bagian Non Internal Umum
Akademik
3. Requirements
3.1 Functional Requirements
Berikut merupakan Functional Requirement dari Sistem Informasi Kegiatan Kampus:
1. Untuk Admin:
2. Untuk Sub-Admin
a. Dapat melakukan proses input, edit, dan delete postingan
Sub-admin, dimana ia adalah seseorang yang diberi tanggung jawab oleh
setiap bidang, memiliki functional sebagai seseorang yang dapat melakukan proses
input (menambahkan data informasi), edit (mengubah data informasi), dan delete
(menghapus data informasi yang sekiranya tidak diperlukan) untuk segala kegiatan
yang dilakukan oleh bagiannya yang bisa diikuti oleh civitas akademika.
Ketika pada nantinya sub-admin sudah memasuki halaman sub-admin, di
sebelah kiri halaman, terdapat menu pilihan yang terdiri dari ketiga proses di atas.
Pada menu edit, dimana ditampilkan seluruh postingan, akan terdapat status,
apakah postingan tersebut telah atau belum di-approve oleh admin.
Jika admin belum meng-approve dalam waktu 1x24 jam setelah postingan
dibuat, sub-admin layak memberikan teguran terhadap admin. Demikian pula
sebaliknya, bila sub-admin tidak melaksanakan tugasnya untuk menginputkan,
maka admin juga berhak menegur.
Account sub-admin berjumlah satu untuk setiap bagian yang telah ditentukan
dan bebas dipakai siapa saja oleh orang yang berada di bagian tersebut.
Tersebarnya account merupakan tanggung jawab koordinator yang ditunjuk oleh
bagian tersebut.
Jika terjadi ke-error-an selama sub-admin menggunakan aplikasi ini, sub-
admin harus segera menghubungi admin, dan kemudian admin yang akan
mencarikan solusinya.
3. Untuk User
a. Dalam versi Mobile
Retention Period
Specify the time for which the data generated by the function would be in use in the
system.
Usability
Usability requirements may include such sub-categories as:
Human factors
Aesthetics
Consistency in the user interface
Online and context-sensitive help
Wizards and agents
User documentation
Training materials
Reliability
Reliability requirements to be considered are:
Frequency/severity of failure
Recoverability
Predictability
Accuracy
Mean time between failure (mtbf)
Performance
A performance requirement imposes conditions on functional requirements. For
example, for a given action, it may specify performance parameters for:
Speed
Efficiency
Availability
Accuracy
Throughput
Response time
Recovery time
Resource usage
Supportability
Supportability requirements may include:
Testability
Extensibility
Adaptability
Maintainability
Compatibility
Configurability
Serviceability
Installability
Localizability (internationalization)
Design Requirements
A design requirement, often called a design constraint, specifies or constrains the
design of a system. Design constraints can be imposed by other standards, hardware
limitations, etc.
Implementation Requirements
An implementation requirement specifies or constrains the coding or construction of a
system. Examples are:
Required standards
Implementation languages
Policies for database integrity
Resource limits
Operation environments
Interface Requirements
An interface requirement specifies
An external item with which a system must interact, or
Constraints on formats, timings, or other factors used by such an interaction.
Standards Compliance
This subsection should specify the requirements derived from existing standards or
regulations.
They might include:
Report format
Data naming
Accounting procedures
Audit Tracing - For example, this could specify the requirement for software to
trace processing activity. Such traces are needed for some applications to meet
minimum government or financial standards. An audit trace requirement might,
for example, state that all changes to a payroll database must be recorded in a
trace file with before and after values.
Hardware Limitations
This subsection could include requirements for the software to operate inside various
hardware constraints. For example, these could include:
Hardware configuration characteristics (number of ports, instruction sets, etc.)
Limits on primary and secondary memory
Number of users the machine can handle at any given time
User Interfaces
This should specify:
1) The characteristics that the software must support for each human interface to the
software product. For example, if the user of the system operates through a display
terminal, the following should be specified:
Required screen format
Page layout and contents of any reports or menu
Relative timing of inputs and outputs
Availability of some form of programmable function keys
2) All the aspects of optimizing the interface with the person who must use the
system. This may simply comprise a list of do's and don'ts on how the system will
appear to the user. One example might be a requirement for the option of long or
short error messages. Like all others, these requirements should be verifiable and for
example, a clerk typist grade 4 can do function X in Z minutes after 1 hr of training
rather than a typist can do function X. (This might also be specified in the Attributes
section under a section titled Ease of Use.)
3) If the user specifies any particular interface that must be present then that must be
documented. Some examples of these interfaces are:
Provision of screen and field level help
Navigating from one function to another
Initializing the screen
Canceling the operation
Screen navigation
Pre-Printed stationeries
Multiple copies or single
80 col. or 132 col.
4. Terms and Conditions
By signing this document, I am agreeing to have provided complete information on the
product that will be developed. The product will be developed according to the specifications
listed in this document unless decreed otherwise By signing this document, I am indicating
that I am satisfied by the information present here and I am giving the company a full go-
head to build the product based on the information listed in this document.