NTNUI Form Management System TDT4290 Customer Driven Project Group 6 Jan Burak Maria Iqbal Siren Finvik Johansen Jonathan Linnestad Erik Liodden Anders Salvesen Kristian Bjørn Thoresen February 11, 2019 Acknowledgements We would like to thank NTNUI, specifically Even Kallevik and Anders Kirkeby. We would also like to thank the TDT4290 course staff, especially our supervisor Katerina Mangaroska. i Contents List of Figures iv List of Tables v 1 Introduction 1 1.1 Project Scope . .1 1.2 Stakeholders . .2 1.3 Report Outline . .2 2 Pre-Study 3 2.1 Organization . .3 2.2 Existing Workflow of the Organization . .4 2.3 Current System - The Member Management System . .4 2.4 Planned Solution - The Form Management System . .4 2.5 Comparison between the Current System and the Planned System . .5 3 Requirement Analysis 6 3.1 User Stories . .6 3.2 Functional Requirements . .7 3.3 Non-Functional Requirements . .7 3.4 Changes in Requirements . .8 4 Project Planning 9 4.1 Project Plan Overview . .9 4.2 Team Organization . 10 4.3 Project Schedule . 10 4.4 Communication . 11 4.5 Documents . 12 4.6 Project Work Organization . 12 4.6.1 Integration of Waterfall with other Methodologies . 13 4.6.2 Working Hours . 13 4.6.3 Meetings . 13 4.6.4 Keeping Time . 15 4.7 Quality Assurance . 15 4.7.1 Time of Response . 15 4.7.2 Code Standards . 15 4.7.3 Code Review and Version Control . 15 4.7.4 Templates and Standards . 16 4.7.5 Testing . 16 5 Risk Management 17 5.1 Risk Table Legend . 17 5.2 Risk Table . 18 5.3 Risk Matrix . 18 5.4 Risks encountered during the Development Phase . 19 6 Methodologies 20 6.1 Adopting the Waterfall Methodology . 20 6.2 Waterfall Methodology in the Project . 20 6.3 Adaptions to the Waterfall Methodology . 21 6.4 Technology and Frameworks . 22 ii 7 Tools 24 7.1 Version Control Management . 24 7.2 Communication and Documentation . 24 7.3 Graphics and Figures . 25 8 Architecture and Design 26 8.1 Architectural Drivers . 26 8.2 Architectural and Design Patterns . 26 8.2.1 Model-View-Template (MVT) . 26 8.2.2 State pattern . 26 8.3 Architectural Tactics . 27 8.3.1 Modifiability Tactics . 27 8.3.2 Security Tactics . 27 8.3.3 Usability Tactics . 28 8.4 Entity Relation Model . 28 8.5 The 4+1 Architectural View Model . 29 8.5.1 Architectural Views . 29 8.5.2 Use Cases . 32 9 Security 34 9.1 Security Features in Django . 34 9.2 Abuse Cases . 34 9.3 Static Security Analysis . 34 10 Testing 36 10.1 Unit and Integration Testing . 36 10.2 Automated Functional Testing . 36 10.3 Usability Testing . 37 10.3.1 Test Preparation . 37 10.3.2 Test Subjects . 38 10.3.3 Test Tasks . 39 10.3.4 Test Proceedings . 39 10.3.5 Test Analysis . 40 11 Final Product 41 11.1 User Guide . 41 11.2 Installation Guide . 43 12 Group Reflection and Evaluation 44 12.1 Description of Group Dynamics . 44 12.2 Reflection on Group Dynamics . 44 12.3 Customer Relations . 44 12.4 What Future Students Should Know . 45 12.5 Feedback on the Course . 45 13 Future Work 46 13.1 Modification of Current System . 46 13.2 Improvements of the FMS . 46 13.3 Suggestions for Future Implementation . 47 13.4 Bugs . 47 References 48 iii A Evolution in Requirements i A.1 Evolution in user stories . .i A.2 Evolution in functional requirements . .i A.3 Evolution in non-functional requirements . ii B Testing iii B.1 User Test Tasks . iii B.2 User Test Introduction . vi B.3 User Test In-depth Analysis . vi C Views vii C.1 Final product . vii C.2 Paper prototype . ..