SOFE3650Guidelines

docx

School

University of Ontario Institute of Technology *

*We aren’t endorsed by this school

Course

3650

Subject

Electrical Engineering

Date

Jan 9, 2024

Type

docx

Pages

Uploaded by DeaconFox2649

Department of Electrical, Computer, and Software Engineering Faculty of Engineering and Applied Science SOFE 3650-Fall 2023 Software Design and Architectures Project Description and Deliverables This document presents a description of the project expectation, deliverables, and grading scheme. Prepared by: Dr. Ramiro Liscano Date: September 2023

SOFE 3650 Project Guideline Author: Dr. Ramiro Liscano Objectives The objective of this project is to demonstrate a methodological set of steps in the design of a software architecture for a set of requirements listed in Appendix A. The expected design approach to take is the Attribute Driven Design (ADD) presented in some detail in the text book [1] and briefly overviewed here. Deliverables The expectation is to submit a set of artifacts in a GitHub classroom repository that your instructor will create for you that demonstrates the ADD steps as applied to the design and implementation of a software application. All deliverables should be uploaded to a GitHub repository that the instructor will set up. Individual contributions in the project will be graded the based-on GitHub commitments of the deliverables and use of the KanBan project board available in GitHub. A good way to manage your project is by leveraging the Issues tagging available through GitHub and the automated KanBan project board. Deliverable 1 – Requirements Analysis (Due Oct 23) Prior to commencing the ADD process the use cases, quality attributes and constraint requirements of the project need to be defined based on the requirements that were provided to you. The format of these submissions should follow closely the FCAPS case example in the text book [1]. Expected artifacts are: • Use Case models • Quality Attributes for the application • System Constraints for the application • Architectural Concerns • Business Case Grading Scheme (worth 25% of total project grade) • Proper identification of the Use Cases • Proper identification of the quality attributes • Proper identification of the constraints and architectural concerns • Clear description of the business case. Deliverable 2 – ADD Iteration 1&2 (Due Nov. 25) At this point in the project you should have gone through the drivers of the project and ready to start he design. Expected artifacts are: • All relevant artifacts from ADD Iterations 1&2

SOFE 3650 Project Guideline Author: Dr. Ramiro Liscano Grading Scheme (worth 50% of total project grade) • Organization and navigation of the GitHub repository with use of README files. • Quality of the 1 st and 2 nd iteration of the ADD steps. o Choice of reference architecture / framework along with justifications o Deployment diagrams o Major components of the architecture o Domain specific components o Interface specification (both internal and external) o Domain specific models Deliverable 3 – Design of a Use Case (Due Dec. 5 – end of the term) At this point the project submission should include all 3 iterations of the ADD. The implementation should follow the architectural model and it should be clear which code files are associated with the design components. The grading of this deliverable is based on how well your team has reviewed the architectural design using the ATAM review process. You should produce a scenario analysis table similar to that presented in Lab 5. Grading Scheme (worth 20% of total project grade) • Organization and navigation of the GitHub repository with use of README files. • The quality of the ATAM scenario analysis Team Assessment (worth 5% of project grade) As a requirement of the course there is a team assessment that should be completed. The purpose of this team evaluation is for students to understand the dynamics and roles of a team. This will be assessed using the ITP metrics tool and instructions will be posted in Canvas. References [1] “Designing Software Architectures: A Practical Approach” by Humberto Cervantes and Rick Kazman and covered in the course.

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

SOFE 3650 Project Guideline Author: Dr. Ramiro Liscano Appendix A: Project Requirements The project you are to design is a course management system (CMS). Below is a list of the requirements for the project. Stakeholders S L A M Students Lecturers Administrators System maintainer General Requirements R1 R2 R3 The system shall provide course information The system shall store course information The system shall be able to represent course information Requirements of Students RS1 The system shall enable students RS2 The system shall facilitate search RS3 The system shall allow students RS4 The system shall allow students RS5 The system shall provide a passw mails it to the user RS6 The system shall notify students RS7 The system shall allow students RS8 The system shall protect the user RS9 The system shall prevent student RS10 The system shall have downtime RS11 The system shall have a maximu RS12 The system shall have a single lo RS13 The system shall have a UI whic according to the intuition of a sta RS14 The system shall have a descript text) RS15 The system shall provide an expo users to import scheduled lecture

SOFE 3650 Project Guideline Author: Dr. Ramiro Liscano Requirements of Lecturers RL1 The system shall allow lecturers RL2 The system shall enable lecturers grade) RL3 The system shall allow lecturers of grades, determining when a st RL4 The system shall enable lecturers RL5 The system shall allow lecturers RL6 The system shall allow lecturers pictures) of people in the system RL7 The system shall allow lecturers RL8 The system shall allow only lectu RL9 The system shall provide grade s department, per year) RL10 The system shall allow lecturers other courses into another course RL11 The system shall allow lecturers RL12 The system shall allow lecturers RL13 The system shall be able to impo the institutions registration syste Requirements of Maintainer RM1 The system shall allow maintain partial system RM2 The system shall allow maintain lecturers and by students RM3 The system shall allow maintain courses RM4 The system shall be easily extens RM5 The system shall be scalable RM6 The system shall be interoperabl Requirements of the Administration RA1 The system shall allow the admin RA2 The system shall allow the admin RA3 The system shall allow the admin students to courses. RA4 The system shall automatically s

SOFE 3650 Project Guideline Author: Dr. Ramiro Liscano RA5 The system shall be interoperable w RA6 The system shall allow the administ student enrolment to courses

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version