Changes between Version 12 and Version 13 of ProjectPhases
- Timestamp:
- 11/11/26 15:17:12 (8 days ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ProjectPhases
v12 v13 1 1 = Project Phases 2 2 3 Project work is done in phases and iterations. Each phase/iteration has to be presented to the teacher during consultations and has to be approved before continuation with the following phases/iterations. If a phase/iteration is not done to a satisfactory level, the team will be instructed to improve their work and present once again for approval. 3 == Method of work (in short) 4 5 * **Project work is done in phases.** 6 * **Each phase has to be presented during consultations and has to be approved before continuation with the following phases.** 7 * **You must document all the work within the phase** at your assigned project website, **before presenting the phase**. Failing to document will postpone the approval. 8 * **Project phases are approved only during consultations.** Approval does not mean the work is finished nor that is correct, it means that your work is to a level that you are allowed to continue with the next phase. 9 * **If a phase is not done to a satisfactory level,** the team will be instructed to improve their work and present once again for approval. 10 11 == Starting a project 12 13 See: [wiki:StartingProjects] 14 15 == Documenting the work on your projects 16 17 **Phase descriptions and requirements listed below and linked on the respective links are from the last year projects and will be revised with the latest requirements until November 22.** 4 18 5 19 Each project phase, iteration and milestone lists the names of the pages that document the respective types of activities in each phase. Create wiki pages in your project site that correspond to these names. As an Example: to document the activity !ProjectVision, create a wiki page named **!ProjectVision**. … … 9 23 **Project phases P0-P4 are mandatory** and must be developed in the same order. **Project phases P5-P9 are elective** -- some of them can be skipped and you can work on them in any order, but it is recommended that you work on P5 first. All phases contribute to your final points and grade. Phases P0-P4 alone are not sufficient to get a passing grade. 10 24 11 == Phase P0: Project Definition25 === Phase P0: Project Definition 12 26 13 27 Describe the project vision and initial data requirements as part of usage scenarios. … … 15 29 See: [[InstructionsP0]] 16 30 17 == Phase P1: Conceptual Model (ERD)31 === Phase P1: Conceptual Model (ERD) 18 32 19 33 Create a detailed model of the data requirements as an Entity-Relationship Model with extensive documentation. … … 21 35 See: [[InstructionsP1]] 22 36 23 == Phase P2: Logical and Physical Design, DB Creation (DDL)37 === Phase P2: Logical and Physical Design, DB Creation (DDL) 24 38 25 39 Implement the database structure from P1 as a relational database schema in a faculty assigned PostgreSQL database, using SQL DDL and DML scripts. … … 27 41 See: [[InstructionsP2]] 28 42 29 == Phase P3: Application Scenarios for DB Access (SQL)43 === Phase P3: Application Scenarios for DB Access (SQL) 30 44 31 45 Increase the level of detail in the usage scenarios with specific database access queries. … … 33 47 See: [[InstructionsP3]] 34 48 35 == Phase P4: First Application Prototype49 === Phase P4: First Application Prototype 36 50 37 51 Create a prototype application that demonstrates how can some of the usage scenarios be implemented, using programming language and technology of your choice. … … 39 53 See: [[InstructionsP4]] 40 54 41 == Milestone M1: First Prototype Public presentation55 === Milestone M1: First Prototype Public presentation 42 56 43 57 * Present the initial version of an application prototype. … … 48 62 Details on the presentations will be announced via course and personal announcements after the end of the lectures in January 2026. 49 63 50 == Phase P5: Normalization64 === Phase P5: Normalization 51 65 52 66 Check the database model using formal methods and improve the model to fix typical problems of un-normalized designs. … … 54 68 See: [[InstructionsP5]] 55 69 56 == Phase P6: Complex DB Reports (SQL, Stored Procedures, Relational Algebra)70 === Phase P6: Complex DB Reports (SQL, Stored Procedures, Relational Algebra) 57 71 58 72 Implement more complex analytical, trend and aggregate data reports using pure SQL and/or store procedures/functions. … … 60 74 See: [[InstructionsP6]] 61 75 62 == Phase P7: Advanced Database Development (SQL DDL)76 === Phase P7: Advanced Database Development (SQL DDL) 63 77 64 78 Implement data constraints, triggers, stored procedures and functions, views. … … 66 80 See: [[InstructionsP7]] 67 81 68 == Phase P8: Advanced Application Development (Transactions, Pooling)82 === Phase P8: Advanced Application Development (Transactions, Pooling) 69 83 70 84 * Implement transactions in the application prototype for usage scenarios that would require transactions. … … 73 87 See: [[InstructionsP8]] 74 88 75 == Phase P9: Other topics (Performance, Security, ...)89 === Phase P9: Other topics (Performance, Security, ...) 76 90 77 91 * Performance analysis of complex queries, indexes. … … 81 95 See: [[InstructionsP9]] 82 96 83 == Milestone M2: Presentation of the final version of the project97 === Milestone M2: Presentation of the final version of the project 84 98 85 99 * Present the finished project and documentation.
