by Ng Kam Hon. / Thesis (M.Sc.)--Chinese University of Hong Kong, 1992. / Includes bibliographical references (leaves 30-31). / Chapter 1. --- Introduction --- p.1 / Chapter 2 --- Project Management --- p.2 / Chapter 3. --- PERT and CPM --- p.3 / Chapter 4. --- Motivation for the proposed automation --- p.4 / Chapter 5 --- The Project Controller --- p.6 / Chapter 5.1 --- General --- p.6 / Chapter 5.2 --- System Design --- p.7 / Chapter 6. --- Project Preprocessing --- p.10 / Chapter 6.1 --- Determining the Earliest Start and Finish --- p.10 / Chapter 6.2 --- Determining the Latest Start and Finish --- p.11 / Chapter 6.3 --- Calculation of free slack and preliminary Schedule --- p.12 / Chapter 7. --- Job Scheduling --- p.13 / Chapter 7.1 --- The Rule Based System --- p.14 / Chapter 7.2 --- The Searcher --- p.17 / Chapter 8. --- Evaluation of the Project Controller --- p.23 / Chapter 8.1 --- Input Project Details --- p.23 / Chapter 8.2 --- Project analysis reports --- p.23 / Chapter 8.3 --- Job Scheduling capabilities --- p.23 / Chapter 9. --- Discussion --- p.27 / Chapter 9.1 --- Applications --- p.27 / Chapter 9.2 --- Future Enhancement --- p.27 / Chapter 9.3 --- Limitations --- p.28 / Chapter 10. --- Conclusion --- p.29 / Chapter 11. --- References --- p.30

M.Ing. (Engineering Management) / Requirements engineering forms an integral part of software engineering. The purpose of requirements engineering is to provide high quality requirements for a system or solution. These requirements are then utilised by developers to produce a high quality system. They also assist project managers to better plan the schedule and costing of information technology projects, resultinq in cost savinqs. The problem is that although formal definitions and processes do exist for requirements engineering, projects are still failing due to the poor quality of requirements, This study investigates this phenomenon, in particular to understand why project teams cannot deliver high quality requirements. This is done against the background of the processes and standards available to organisations. The root cause of the problem is researched to determine whether the processes are the cause or whether other factors are contributing to poor quality requirements. This study makes use of two cases within one organisation to determine what the contributing factors are with regard to poor and good quality requirements. The cases provide information on why one project delivered good quality requirements and another project within same organisation, the same business unit, with the same support structure, delivered poor quality requirements. It is perceived that the case study method was a valid method in this particular research study as it provided the researcher with in-depth knowledge and observations on how organisations deal with the process of requirements engineering. It was found that the quality and clarity of communication or the lack thereof plays a significant role in the quality of requirements. This research provides an alternative view on the factors contributing towards poor quality requirements. This implies that organisations can train or educate requirements engineers in communication skills. The skill of communication allows a requirements engineer to create a trust relationship with customers, and this empowers him/her to elicit good quality requirements from the users.

Thesis. 1977. M.S.--Massachusetts Institute of Technology. Dept. of Civil Engineering. / MICROFICHE COPY AVAILABLE IN ARCHIVES AND ENGINEERING. / Bibliography : leaves 82-83. / M.S.