• 1

pulsar, pulsar consulting

Technical Analysis

Technical implementations of the functional rules described during functional analysis: 

  • Pseudo-Code
  • Very detailed Architecture document & Explanations
  • Explanation on Technical Mechanisms

 

Associated methodology documents : 

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 in A3 or A4 format 

TEC-< Client>-< Project>-[Topic]-[Doc_Version].doc (Path: < Project>\Docs\Server) Document containing the technical explanation of the Code and Module structure on the server side (Middle Tier) 

CLASS-< Client>-< Project>-[Doc_Version].doc (Path: < Project>\Docs\Server) Document containing the Classes Diagram and explanations of each classes 

INST-< Client>-< Project>-[Doc_Version].doc (Path: < Project>\Docs\Architecture) Full Installation Procedure, explaining how to install the application from scratch using the installation CD-ROM, and all needed applications for this project (generally it is supposed that the OS and DB instance exist). 

INST-< Client>-< Project on GID>-[Doc_Version].doc (Path: < Project>\Docs\Architecture) Light Installation Document, explaining how to install an application on GID platform from scratch using the installation CD-ROM 

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 

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). 

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 

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) 

DEPLOY-< Client>-< Project>-[Doc_Version].doc (Path: < Project>\Docs\Pulsar Internal) Internal document explaining how to technically deploy the application and generate the executable files in order to run it in Pulsar Environment (Jar Deployment, DLLs, etc…) 

PACK-< Client>-< Project>-[Doc_Version].doc (Path: < Project>\Docs\Pulsar Internal) Internal document explaining how to Package the application and create the installation CD-ROM that will be delivered to the customer