Scribd
Upload
33 views2 pages

FS Review Comments FMS

The Functional Specification (FS) document for the Financial Management System (FMS) of PCSIR is incomplete, covering only a small portion of the system and lacking essential modules and mockups. There are inconsistencies in field labels, actor designations, and missing non-functional requirements, such as security measures and system architecture. Additionally, the document fails to address how scanned documents will be managed and does not include the joint venture's name in the header.

Uploaded by

younas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
33 views2 pages

FS Review Comments FMS

The Functional Specification (FS) document for the Financial Management System (FMS) of PCSIR is incomplete, covering only a small portion of the system and lacking essential modules and mockups. There are inconsistencies in field labels, actor designations, and missing non-functional requirements, such as security measures and system architecture. Additionally, the document fails to address how scanned documents will be managed and does not include the joint venture's name in the header.

Uploaded by

younas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Functional Specification Document Review For For FMS

 The FS document provided by Biafotech does not comprehensively cover


the entire Financial Management System (FMS) of PCSIR. It only
includes 3–4 modules, representing less than 10% of the complete
system. Major functional areas such as Pension Branch, Audit Branch,
Disbursement Branch, GP/CP Fund etc. are missing.
 Some modules are listed without corresponding mockups. For example,
reference 3.5.4 (page 61) mentions a main success scenario, but no
mockup or UI is provided for the "Filing SGI form and submission to
head office". This issue needs to be reviewed across all modules.
 Each sub-module should contain a high-level description and the purpose
of the specifications defined within that sub-module.
 There are mismatches between field labels and their types. For instance,
on page 82, “Budget head” is shown as a search field but is displayed as a
dropdown. On page 85, “Print, Export, Download” are action buttons
labeled as “Read” with no associated error messages. This inconsistency
must be reviewed throughout the document.
 The FS document includes designations like “Finance Officer” and
“Account Admin”, which do not exist in PCSIR. Additionally, “Account
Admin” (which should be corrected to “Account Assistant”) is incorrectly
listed as the primary actor. All actors in the document must be thoroughly
reviewed and corrected.
 There are spelling and labeling inconsistencies in field names. For
example, on page 12, “Created by” is mentioned twice, while the mockup
displays it as “Created at”.
 The document does not include any non-functional requirements such as
security, user authentication, role-based access control, system
performance, or scalability parameters.
 A high-level system architecture diagram is missing, making it unclear
how different modules interact, their hierarchy, and overall data flow
within the system.
 On page 62, when a filter is applied, no data appears for the fiscal year
along with date information for that fiscal year, and the corresponding
report format for printing is also not provided (as per PCSIR provided
Format).
 The FS document fails to specify how scanned documents are to be
handled. There is no mention of maximum allowed file size, or
designated storage location, despite multiple fields requiring attachments
(e.g., pages 50 and 53).

Digital Transformation, Strengtheing and Automation of PCSIR 1


Functional Specification Document Review For For FMS

 Although the project was awarded to the joint venture of M/s Biafotech
and M/s Hisper Technologies, the FS document only features the logo and
name of M/s Biafotech. It is recommended to include the name of the
joint venture in the document header and title.
 The FS document does not specify the security measures or encryption
techniques that will be used to ensure data protection within the system.

Digital Transformation, Strengtheing and Automation of PCSIR 2

You might also like