3 Cr. (Hrs.:3 Lec.)
This two semester sequence is the capstone course for a Software Engineering degree. Students will work in teams of one to five under the direction of the instructor to either develop or re-engineer a complex software product. Although a variant of an Agile process will be used, the team will produce or review all the traditional software engineering pre-implementation work products (at least in draft form). In this first semester each team will review or develop documents such as a Software Concept of Operation document, a Software Requirements Specification, a Software Development Plan, a Software Design Description, a Configuration Management Plan, a Software Quality Assurance Plan, and a Software Test Plan/Report, in accordance with the Montana Tech Methods software development standards. Other documents may also be required for a project. ESOF 486 will probably also include the development or demonstration of exploratory prototypes including the possibility of virtual reality prototypes. Prerequisites: ESOF 326 & ESOF 328, CSCI 340 or CSCI 443, or COMX 338. Co-requisite ESOF 427 & ESOF 411. (1st, 2nd) ESOF 486/487 must be taken in sequence. In unusual personal circumstances 487 may be taken a year after 486.
Need a total of 6 credits and have to do 3 credits at time. (1st)
E1. The student must have good knowledge of programming (from CSCI 136 and CSCI 332), algorithm design and analysis (from CSCI 232, CSCI 332 and ESOF 427), databases (from CSCI 340 or BMIS 375) and software engineering (from ESOF 322, ESOF 326, ESOF 328 and COMX 338).
E2. The student should be able to write software development documents: a Software Requirements Specification (from ESOF 328), a Software Design Description and a Software Test Plan/Report (from ESOF 326 or ESOF 411).
E3. The student should be able to quickly learn to use a high level programming language necessary for the assigned project.
R1. Will have demonstrated the ability to work effectively in a team setting on a multi-programmer, multi-month and multi-phase software project. (EAC-a, c, e, g, i, k; 1, 2, 3, 4)
R2. Will be able to describe and discuss the professional and ethical responsibilities related to their project and similar projects. (EAC-f, g)
R3. Will have demonstrated the ability to interact effectively with a client or customer in eliciting and/or verifying system requirements. (EAC-c, e, g, k; 1, 3)
R4. Will have demonstrated the ability to have developed or modified software requirements and specifications for a software system.
R5. Will have demonstrated the ability to develop a software development plan.
R6. Will have demonstrated the ability to describe a system/module design by creating or extensively modifying a software design description. (EAC-a, c, k; 1, 2, 3)
R7. Will have demonstrated the ability to develop a software test plan/report.
R8. Will have demonstrated the ability to rigorously inspect or review all of the software engineering documents used in their project. (EAC-a, k; 1, 2, 3)
R9. Will have demonstrated a working knowledge of software version and change management control. (EAC-a, k; 1, 2, 3)
R10. Will have demonstrated a working knowledge of all the software development tools used in the development of the project's product. (EAC-a, i, k; 1, 2, 3)
R11. Will have demonstrated an understanding of the impact of engineering solutions in a global, economic, environment and societal context. (EAC-h)
R12. Will have demonstrated an understanding of contemporary issues. (EAC-j)