FSD Mints
FSD Mints
DOCUMENT HISTORY
Date Version Document Revision Description Document Author
APPROVALS
Approval Approved
Approver Role Approver
Date Version
DOCUMENTS DESCRIPTION
Title Description
Page 2
Tgl Diciptakan 20-Mei-2019
Tgl Direvisi
Page 3
Table of Contents
1. Introduction .......................................................................................................................................... 5
1.1 Purpose of the document ............................................................................................................. 5
1.2 Project Scope ................................................................................................................................ 6
1.3 Scope of the document ................................................................................................................. 6
1.4 Related documents ....................................................................................................................... 6
1.5 Terms/Acronyms and Definitions............................................................................................... 6
1.6 Risks and Assumptions ............................................................................................................... 6
2. System/ Solution Overview .................................................................................................................. 7
2.1 Context Diagram/ Interface Diagram/ Data Flow Diagram, Application Screen Flow, Sitemap,
Process Flow ......................................................................................................................................... 7
2.2 System Actors .............................................................................................................................. 7
2.3 Dependencies and Change Impacts ............................................................................................... 7
3. Functional Specifications ...................................................................................................................... 7
3.1 <Title> ............................................................................................................................................. 8
4. System Configurations ........................................................................................................................ 10
5. Other System Requirements/ Non-Functional Requirements ........................................................... 10
6. Reporting Requirements..................................................................................................................... 11
7. Integration Requirements................................................................................................................... 11
7.1 Exception Handling/ Error Reporting .......................................................................................... 11
8. Data Migration/ Conversion Requirements........................................................................................ 11
8.1 Data Conversion Strategy ........................................................................................................... 11
8.2 Data Conversion Preparation ...................................................................................................... 12
8.3 Data Conversion Specifications ................................................................................................... 12
9. References .......................................................................................................................................... 12
10. Open Issues ..................................................................................................................................... 12
Appendix ..................................................................................................................................................... 12
Page 4
1. Introduction
PT Murni Solusindo Nusantara dalam menjalankan bisnisnya dengan menjual produk dan memberikan
layanan-layanan baik itu berupa preventive maintenance maupun corrective maintenance. Layanan-
layanan ini tentunya hanya dapat diberikan secara optimal kepada customer-customer dari PT Murni
Solusindo Nusantara dengan dukungan logistik dan manajemen tugas yang baik.
Secara pengelompokan after-sales service, customer dari PT Murni Solusindo Nusantara dibagi menjadi
2 jenis layanan yaitu:
BPO (Business Process Outsourcing), yaitu customer menyewa alat-alat dari PT MSN
Non BPO, yaitu customer membeli putus alat-alat dari PT MSN
Untuk menunjang hal tersebut maka diperlukan suatu sistem informasi yang mampu mengoptimalkan
semua elemen tersebut.
MINTS
Functional specification menggambarkan bagaimana sebuah produk harus berjalan dari sudut pandang
user, tidak perduli dengan bagaimana hal itu diimplementasikan dan hanya membicarakan fitur serta
membicarakan tentang tampilan layar, menu, dialog, dan seterusnya.
FSD adalah semacam pedoman atau sebagai titik acuan developer untuk menuliskan kode
pemrograman. Sebuah spesifikasi fungsional juga berisi deskripsi formal tugas-tugas pengguna,
ketergantungan pada produk lainnya, dan kegunaan dari tiap produk yang dibuat.
Page 5
1.2 Project Scope
Kebutuhan dalam sebuah proyek MINTS antara lain :
Page 6
2. System/ Solution Overview
<Provide a short description of the software and solution being specified and its purpose, including
relevant benefits, objectives, and goals.>
3. Functional Specifications
<Start describing the specifications related to the overall system here. You may want to create a table/
index of all functionalities explained in the sections below and link them to the items below>
<If no separate reference/ traceability document is created for the project, use this section to map the
business requirements, use cases, functional requirements and the test cases>
<Group your functional specifications as appropriate for your project. You may want to divide them by
screens, functional areas, user role, JIRA tickets or high-level functions Vs detailed functions or any other
way that works for your project>
Page 7
3.1 <Title>
3.1.1 Purpose/ Description
<Include a high-level description and purpose of the specifications covered in the section.>
<List any extended steps/ scenarios that occur, other than the main success
scenario.>
Priority <indicate priority of high, medium or low)
Special Requirements <Any system related special requirements needed to fulfill the use case>
Open Questions <Notes and questions>
3.1.3 Mock-up
<Provide the mock-up of the functionality or a mock-up of the entire page>
Make sure each specification has a reference number and is explained in the following format.>
Page 8
<Note: Section 3.1.4 and section 3.1.5 may be combined if there are a few functionalities on a particular
page>
Form Elements:
Data
Validation / Business Rules Additional
Field Label Error Messages Dependenci
Info/ Notes
es
<Label name> <Specify the validation rules and/ <List the error message <Specify if <Provide any
or business rules applicable to the that should be displayed there are additional
form element> and under what any date information
conditions> dependencie here>
s>
Example: User name User name shall be a valid For incorrect user name None Access
Stanford Sunet ID display on setFocusOff: prohibited
“Please provide a valid only to
user name” Stanford
affiliates. For
non-Stanford
affiliates,
check call-out
3.1
Buttons, Links and Icons:
Page 9
<Button <Specify <Specify the <Specify <Specify if <Specify the <Specify the <Mention if there
label the operation that default button is link where validation are any
name> operation would be visibility enabled or the page will rules on dependencies on
that would performed on of the disabled be re- operation of other form
be other events> button> and the directed, if the button> elements and/ or
performed condition, if any> buttons>
on an on- any>
click
event>
Example: Verify if OnMouseHover Yes, Disabled, by User Verify if Disable the New
Submit user name display the always default. Dashboard Username is a user functionality
and following Enabled, page valid sunet ID on subsequent
password message: after first and user pages if user logs in
are correct. “Please provide key entered name and through this
If yes, log your web- in either password button.
the user authentication username or match with
into the details to sign password registry data.
system. in> field.
4. System Configurations
<Provide an overview of all the steps or the set ups required to configure an application/program. Also
state the intent or purpose behind each set up or configuration. Discuss the possible alternatives,
customizations, workaround’s, conditions and dependencies in a particular configuration. In case of
Oracle applications, please list all applicable BR100’s or Application set up documents>
6. Reporting Requirements
<This section is used to capture the reporting needs, including but not limited to the scope and format of
the report, data elements and contents required on the report, file types and extraction mechanisms,
user base and accessibility levels, frequency of report extractions etc. Also provide the mock up of the
report if needed. If necessary, create a separate document for reporting requirements.>
7. Integration Requirements
<Identify the integration needs and state all required interfaces with anything external to this solution
including hardware, software, and users. Include Architectural overview diagrams, high level data flow
diagrams, table structures and schema, interface protocols, API’s, Error conditions, Error validations and
messaging needs, Auto processing requirements etc. You can optionally state hardware and software
dependencies, Upgrade requirements, compatibility issues with existing frameworks and solutions, etc>
9. References
<List all references to external material used as background information or knowledge for the FSD.
Examples may include a compliancy website, Stanford website, etc>
Appendix
Page 12