Topic: Requirements Documentation Select a project/ system you are familiar with – o Unclassified o Not proprietary Locate this project’s needs and/or requirements documentation (e g Operational Requirements Document (ORD), Capability Development Document (CDD), System Requirements Document (SRD), Functional Requirements Document (FRD) (hint: usually has lots of “shall” statements in it) Review the Needs/Requirements Documentation Describe: – – What appear to be the goals of the project? What is the viewpoint(s) taken by the document’s authors (who’s perspective are they representing? the user, the developer, the buyer?) How is the requirements document structured? Do you have any issues with the way the authors present the information? What sort of requirements errors do you see? (look at the what SEH v4 says are important factors-also Davis’ Quality Factors from the Lecture 6 slides) 1. 2. 3. 4. 5.
Enterprise Resource Planning (ERP) for educational institutions (Here in after called as ERP System)
1. The goals:
- To link all departments of the university like chemical engineering, mechanical engineering, civil engineering, electronics engineering, electrical engineering, computer science and engineering, and Aeronautical engineering into one common cloud computing platform
- To integrate the data entry and information maintenance roles into a common application
- To replace all the 3rd party applications like word, excel, account mate (accounting software), Nirmal, Opaque library software, Tally accounting packages, and many other smaller software being used all over the group of educational institutions
- This single ERP system will provide a snap shot of the entire group for the top management to view from their laptops.
The buyer’s perspective is represented by the author.
The buyer’s situation and their perspective are as listed below:
- The buyer or client is a chain of educational institutions consisting of 12 primary schools, 10 secondary schools, 20 tertiary educational institutions like poly techniques, and colleges including engineering colleges and medical colleges
- The total students strength includes a population base of 45,000
- The total staff strength including lecturers, assistant professors, associate professors, principals, dean, guest lecturers, faculties, support staff, cleaners, janitors, office bearers, office boys, and peons include a population base of 10,000
- Hence the client want a single look up facility for the top management to see the status of this entire population of 55,000 stake holders (both students and employees)
The requirement document is not properly structured and there is lots of scope for improvement
- They did not follow the recommendations made by the Institute of Electrical and Electronic Engineers (IEEE) standards neither the American Nationals Standards
- The scope and feasibility were not clearly mentioned
- They did not say what the ERP will do and more importantly what the ERP will not do
- The objectives were not represented properly – the pay backs they will reap out as a result of installation of this ERP was not indicated clearly – it was just vaguely abstracted
- The stake holders have to figure it out from the design specifications and the user’s manual but it must have been listed in the requirements specification in the first place.
The author is not presenting the information in a systematic and well organized manner – it is not ordered in any set sequence – neither chronological nor functionality based.
It would have better if the author followed the following style:
- Align the matter in the requirement specification along with that in the documents in the higher levels in the document hierarchy
- A separate section for defining the technical jargons like PHP is a programming language, mySQL is a database, tables are entities in a data base, Records are horizontal entries of a table, while columns are vertical entries of a table, etc must have been mentioned
- There were no sections on citations, reference, or checklists
- Data dictionary was missing as well
- The document change history was not maintained by the author – so the clients do not know who changed what and when and why
Providing index, glossary, acronyms are essential to explain the technical jargons used in the terminology and writing style.
Feasibility report on what possibly can be done and what are beyond the scope of the project.
Make sure that the requirements are independent and on their own, and it does not involve other dependants to fully qualify them.