• 1

pulsar, pulsar consulting

Functional Analysis

Based on the BUSREQ and ARCREQ, this phase describes how the application will functionally implement the requirement, producing the following documents: 

  • Detailed Architecture Document including general & detailed data flows and explanations
  • Detailed Data Structure definition: entity-relationship diagram (ERD) and explanations, data diagram (DD) and explanations
  • Screens Design (Use Case or GUI Document)
  • Functional Rules

Customer agreement needed to proceed to next step: this agreement can eventually be done by functional module if no interdependencies, allowing parallelizing a part of the analysis and the development. No development is done without client agreement on the analysis documents.


Associated methodology documents : 

ARC-< Client>-< Project>-[Topic]-[Doc_Version].doc (Path: < Project>\Docs\Architecture) Updating and improving of the ARCREQ document, describing the complete system architecture, Document describing all the System Architecture (general and detailed flow diagrams). 

ARC-DIAGRAM-< Client>-< Project>-[Topic]-[Doc_Version].vsd (Path: < Project>\Docs\Architecture\ARC-Design) The MS-Visio diagrams (screenshots in the doc are made from these diagrams) 

ARC-SITEMAP-< Client>-< Project> -[Doc_Version].vsd (Path: < Project>\Docs\Architecture\Site-Web-Map) The MS-Visio diagrams of the site structure and navigation (possible screenshots in the doc are made from this diagram also) 

GUI-< Client>-< Project>-[Doc_Version].doc (Path: < Project>\Docs\Client) Document describing all the application screens and explanations on the behaviour of each element (button, field, checkboxes, menu items, radio buttons, list-boxes, etc…) 

DB-< Client>-< Project>-[Doc_Version].doc (Path: < Project>\Docs\Server) Document describing the Entity Relationship Diagram or the Conceptual Data Model (CDM) 

DB-DIAGRAM-< Client>-< Project>-[Doc_Version].cdm or .pdm (Path: < Project>\Docs\Server\DB-Design) ERD/CDM diagram and, if the case, the DD/PDM, (screenshots in the doc are made from these diagrams) 

TEST-< Client>-< Project>-[Doc_Version].mdb (Path: < Project>\Tests) Database containing the Test Flows and Cases of the Application (Business, Functional and Technical Tests Flows), the tests results and the description of the found problems and their resolution. 

MM< nr>-< Client>-< Project>-< Date>-[Topic].doc (Path: < Project>\Docs\Follow-up) Minutes of the meetings with the clients; (Path: < Project>\Docs\Pulsar Internal) Minutes of the internal meetings 

QUES-< Client>-< Project>-[Doc_Version].xls (Path: < Project\Docs\Request&Proposals) Listing of all the questions that are raised during the project and needs to be asked to the client 

TASK -< Client>-< Project>-[Doc_Version].xls (Path: < Project\Docs\Pulsar Internal) Distribution of the tasks across the team, 

ENH-< Client>-< Project>-[Doc_Version].xls (Path: < Project\Docs\Request&Proposals) Listing of the known future enhancements (that means specifying what’s outside the scope of the project). 

DELIV-LIST-< Client>-< Project>-[Doc_Version].xls (Path: < Project\Docs\Request&Proposals) Listing of the deliverables to be delivered to the client at the end of the project. 

PROJ-PLAN< Client>-< Project>-[Doc_Version].mpp (Path: < Project>\Docs\Request&Proposal) Planning of the project (Example: MPP file), often in Gantt-Chart form, including if needed the resource allocation. 

PROJ-PROGRESS< NR>-< Client>-< Project>-< Date>-[Doc_Version].doc (Path: < Project>\Docs\Follow-up) Project Progress Report (follow-up of the project status) 

UMAN-< Client>-< Project>-[Doc_Version].doc (Path: < Project>\Docs\Client) User Manual of the Application 

HELP-< Client>-< Project>-[Doc_Version].html (Path: < Project>\Docs\Client) Help Document and FAQ