Software Requirements Specification
for
<Rancang Bangun Aplikasi Transaksi Toko ATK >
Version 1.0
Prepared by <Adelia Octaviani - 20312103>
<Adella Widiyanti - 20312146>
<Dwi Indriati - 20312041>
<Sodikin - 20312074>
<organization>
<24 May 2022 >
Table of Contents
Table of Contents ii
Revision History ii
1. Introduction 1
1.1 Purpose 1
1.2 Document Conventions 1
1.3 Intended Audience and Reading Suggestions 1
1.4 Product Scope 1
1.5 References 1
2. Overall Description 2
2.1 Product Perspective 2
2.2 Product Functions 2
2.3 User Classes and Characteristics 2
2.4 Operating Environment 2
2.5 Design and Implementation Constraints 2
2.6 User Documentation 2
2.7 Assumptions and Dependencies 3
3. External Interface Requirements 3
3.1 User Interfaces 3
3.2 Hardware Interfaces 3
3.3 Software Interfaces 3
3.4 Communications Interfaces 3
4. System Features 4
4.1 System Feature 1 4
4.2 System Feature 2 (and so on) 4
5. Other Nonfunctional Requirements 4
5.1 Performance Requirements 4
5.2 Safety Requirements 5
5.3 Security Requirements 5
5.4 Software Quality Attributes 5
5.5 Business Rules 5
6. Other Requirements 5
Appendix A: Glossary 5
Appendix B: Analysis Models 5
Appendix C: To Be Determined List 6
Revision History
Name Date Reason For Changes Version
1. Introduction
1.1 Purpose
Dokumen ini menjelaskan tentang spesifikasi persyaratan perangkat lunak Aplikasi Kasir Toko ATK. Tujuan penulisan dokumen ini adalah untuk memberikan penjelasan mengenai perangkat lunak yang akan dibangun.
1.2 Document Conventions
<Describe any standards or typographical conventions that were followed when writing this SRS, such as fonts or highlighting that have special significance. For example, state whether priorities for higher-level requirements are assumed to be inherited by detailed requirements, or whether every requirement statement is to have its own priority.>
1.3 Intended Audience and Reading Suggestions
Pengguna dari dokumen ini adalah pengembang petrangkat lunak Aplikasi Kasir Toko ATK pengguna (user) dari perangkat lunak atau personil-personil yang terlibat dalam sistem. Dokumen ini akan digunakan sebagai bahan acuan dalam proses pengembangan dan sebagai bahan evaluasi pada saat proses pengembangan perangkt lunak maupun di akhir pengembangannya. Dengan adanya dokumen ini diharapkan pengembangan perangkat lunak akan lebih terarah dan lebih terfokus serta tidak menimbulkan ambiguitas bagi pengembang perangkat lunak Aplikasi Kasir Toko ATK.
1.4 Product Scope
Perangkat lunak yang akan dikembangkan adalah perangkat lunak Aplikasi Kasir Toko ATK, yaitu merupakan perangkat lunak yang digunakan untuk mempermudah proses administrasi dan jual beli ATK. Sistem mampu melayani pemilihan barang yang dibeli dan perhitungan harga dari barang yang di pilih. Admin dan karyawan dapat melihat rekapitulasi hasil penjualan dan hasil pembelian.admin dan karyawan dapat melihat persediaan barang.
1.5 References
http://pramdana.blogspot.com/?view=magazine https://dokumen.tips/documents/srs-sistem-informasi-jual-beli-obat-pada-apotek.html
2. Overall Description
2.1 Product Perspective
Adapun gambaran perancangan dan desain aplikasi kasir Toko ATK dapat dilihat pada bagan berikut :
2.2 Product Functions
Fungsi dari perangkat lunak Aplikasi Kasir Toko ATK ini adalah untuk merekam semua kegiatan yang berhubungan dengan proses transaksi di dalam penjualan. Selain itu juga dapat memudahkan perusahaan membuat dokumen- dokumen seperti penawaran, Invoice, SO, dll
2.3 User Classes and Characteristics
Adapun user karakteristik dari pengguna Aplikasi Kasir ini adalah sebagai berikut :
User Jumlah Kriteria
Administrasi 1 1. Melakukan semua fungsi administrasi
2. Melakukan fungsi Supervisor dan operator
Supervisor 1 1. Memonitor laporan transaksi
2. Melakukan konfirmasi atas perubahan data stock barang yang dilakukan oleh operatot
3. Melakukan fungsi operator
Operator 1 1. Merekam semua kegiatan transaksi kedalam aplikasi
2. Membuat dokumen-dokumen yang dibutuhkan
2.4 Operating Environment
<Describe the environment in which the software will operate, including the hardware platform, operating system and versions, and any other software components or applications with which it must peacefully coexist.>
2.5 Design and Implementation Constraints
<Describe any items or issues that will limit the options available to the developers. These might include: corporate or regulatory policies; hardware limitations (timing requirements, memory requirements); interfaces to other applications; specific technologies, tools, and databases to be used; parallel operations; language requirements; communications protocols; security considerations; design conventions or programming standards (for example, if the customer’s organization will be responsible for maintaining the delivered software).>
2.6 User Documentation
<List the user documentation components (such as user manuals, on-line help, and tutorials) that will be delivered along with the software. Identify any known user documentation delivery formats or standards.>
2.7 Assumptions and Dependencies
Asumsi yang ada pada proses perencanaan yang telah dibuat dalam proyek rekayasa perangkat lunak tersebut adalah :
1. Proyek tidak akan berubah selama masa pengerjaan proyek ini
2. Sumber daya teridentifikasi akan terrsedia atas permintaan
3. Pendanaan telah disetujui akan tersedia atas permintaan
3. External Interface Requirements
3.1 User Interfaces
3.2 Hardware Interfaces
Tidak ada hardware interfaces dalam perangkat lunak yang akan di kembangkan
3.3 Software Interfaces
Pada penerapan proyek ini menggunakan Three Tier. Aplikasi client berupa aplikasi yang memiliki kemampuan membaca kode program yang dikirim oleh web server menjadi objek grafik. Server apliaksi bertanggung jawab mengelola komponen logika aplikasi yang akan ditampilkan pada aplikasi client. Komponen database disebar pada tier 3(sever database). Client hanya bisa membaca interpretasi dari server aplikasi atau web server, sedangkan server aplikasi adalah yang mengelola data server sebuah aplikasi dan data tersebut terletak pada server.
3.4 Communications Interfaces
Tidak seberapa perlu adanya antar muka khusus untuk interkoneksi dalam database server, namun tetap membutuhkan suatu jaringan yang cukup stabil dan reliable untuk proses transfer data dari client ke server atau sebaliknya.
4. System Features
<This template illustrates organizing the functional requirements for the product by system features, the major services provided by the product. You may prefer to organize this section by use case, mode of operation, user class, object class, functional hierarchy, or combinations of these, whatever makes the most logical sense for your product.>
4.1 System Feature 1
<Don’t really say “System Feature 1.” State the feature name in just a few words.>
4.1.1 Description and Priority
<Provide a short description of the feature and indicate whether it is of High, Medium, or Low priority. You could also include specific priority component ratings, such as benefit, penalty, cost, and risk (each rated on a relative scale from a low of 1 to a high of 9).>
4.1.2 Stimulus/Response Sequences
<List the sequences of user actions and system responses that stimulate the behavior defined for this feature. These will correspond to the dialog elements associated with use cases.>
4.1.3 Functional Requirements
<Itemize the detailed functional requirements associated with this feature. These are the software capabilities that must be present in order for the user to carry out the services provided by the feature, or to execute the use case. Include how the product should respond to anticipated error conditions or invalid inputs. Requirements should be concise, complete, unambiguous, verifiable, and necessary. Use “TBD” as a placeholder to indicate when necessary information is not yet available.>
<Each requirement should be uniquely identified with a sequence number or a meaningful tag of some kind.>
REQ-1:
REQ-2:
4.2 System Feature 2 (and so on)
5. Other Nonfunctional Requirements
5.1 Performance Requirements
<If there are performance requirements for the product under various circumstances, state them here and explain their rationale, to help the developers understand the intent and make suitable design choices. Specify the timing relationships for real time systems. Make such requirements as specific as possible. You may need to state performance requirements for individual functional requirements or features.>
5.2 Safety Requirements
<Specify those requirements that are concerned with possible loss, damage, or harm that could result from the use of the product. Define any safeguards or actions that must be taken, as well as actions that must be prevented. Refer to any external policies or regulations that state safety issues that affect the product’s design or use. Define any safety certifications that must be satisfied.>
5.3 Security Requirements
<Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. Define any user identity authentication requirements. Refer to any external policies or regulations containing security issues that affect the product. Define any security or privacy certifications that must be satisfied.>
5.4 Software Quality Attributes
<Specify any additional quality characteristics for the product that will be important to either the customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various attributes, such as ease of use over ease of learning.>
5.5 Business Rules
<List any operating principles about the product, such as which individuals or roles can perform which functions under specific circumstances. These are not functional requirements in themselves, but they may imply certain functional requirements to enforce the rules.>
6. Other Requirements
<Define any other requirements not covered elsewhere in the SRS. This might include database requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so on. Add any new sections that are pertinent to the project.>
Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms specific to a single project in each SRS.>
Appendix B: Analysis Models
<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-transition diagrams, or entity-relationship diagrams.>
Appendix C: To Be Determined List
<Collect a numbered list of the TBD (to be determined) references that remain in the SRS so they can be tracked to closure.>
