MV042 | Project (2) |
Teaching Staff in Charge |
Prof. PÂRV Bazil, Ph.D., bparvcs.ubbcluj.ro |
Aims |
At the completion of this course, the student should:
- have documentation abilities on an established topic - be able to write a document on an established topic and with a pre-defined structure (dissertation) - analysis, synthesis and critical skills - be able to develop a software system on a given topic (domain). |
Content |
Project activities in both semesters are individual activities performed by each student as part of the preparation of its/hers dissertation thesis.
From a structural viewpoint, a dissertation will have three parts: - conceptual - technological - applicative. In the first term, the goal of project activities is to obtain a draft version of the conceptual part of the dissertation thesis. They are: 1. Bibliographical documentation and the first draft of the technological part - due week 3 2. Application: requirements analysis (including documentation) - due week 5 3. Intermediate versions of conceptual and technological parts - due week 7 4. Final versions of conceptual and technological parts - due week 8 5. Application: design (including documentation) - due week 9 6. Application: coding, testing, documentation - due week 12. |
References |
1. Enterprise JavaBeans 3 Specification, Sun Microsystems, http://java.sun.com/products/ejb/docs.html
2. Java Enterprise Edition, Sun Microsystems., 1999. http://java.sun.com/javaee/index.jsp 3. Matena, V et al., Applying Enterprise JavaBeans 2.1: Component-Based Development for the J2EE Platform, Addison-Wesley, The Java Series, 2003. 4. Ed Roman et al., Mastering Enterprise JavaBeans 3rd ed., Wiley, 2005. (free pdf version available at http://www.theserverside.com/tt/books/wiley/masteringEJB/) 5. Enterprise Solution Patterns using Microsoft .NET, Microsoft Patterns and Practices Home, http://msdn.microsoft.com/practices/. 6. Application Architecture for ,NET. Designing Applications and Services, Microsoft Patterns and Practices Home, http://msdn.microsoft.com/practices/. |
Assessment |
Modul de evaluare (le)
1. technological part v1 20% 2. app requirements 10% 3. conceptual and technological parts v2 10% 4. conceptual and technological parts final version 20% 5. app design 20% 6. app coding, testing, documentation 20% Each of the activities above has a due date and a corresponding mark, on a 10-point scale. A penalty of 1pt per week are considered for delays. The weights are as follows: The final mark is computed as an weighted average of the marks for individual activities. |
Links: | Syllabus for all subjects Romanian version for this subject Rtf format for this subject |