Presentation is loading. Please wait.

Presentation is loading. Please wait.

SIM5113 - SOFTWARE ARCHITECTURE Instructor: Masrah Azrifah Azmi Murad, PhD Room: C2.11 Email: masrah.azrifah [at] gmail.com OR masrah [at] fsktm.upm.edu.my.

Similar presentations


Presentation on theme: "SIM5113 - SOFTWARE ARCHITECTURE Instructor: Masrah Azrifah Azmi Murad, PhD Room: C2.11 Email: masrah.azrifah [at] gmail.com OR masrah [at] fsktm.upm.edu.my."— Presentation transcript:

1 SIM5113 - SOFTWARE ARCHITECTURE Instructor: Masrah Azrifah Azmi Murad, PhD Room: C2.11 Email: masrah.azrifah [at] gmail.com OR masrah [at] fsktm.upm.edu.my Course website: http://csnotes.upm.edu.my/kelasmaya/pgkm20910.nsf/ http://csnotes.upm.edu.my/kelasmaya/pgkm20910.nsf/ Consultation Hours: By appointment.

2 Synopsis  This course covers the concepts, principles, and state-of-the-art methods in software architectures, including domain-specific software architectures (DSSA), architectural styles, architecture description languages (ADL), software connectors, dynamism in architectures, and architecture-based analysis and testing. In the process of studying these concepts, it also focuses on relationship to other areas of software engineering, specifically the requirements, design, and implementation.

3 Objectives  Analyzing requirements and build software architecture framework  Critic issues in software development and framework  Relate software architecture concept with other areas of software engineering, specifically the requirements, design, and implementation  Be able to lead a software development project

4 Evaluation  Assignments 10%  Project30%  Participation10%  Midterm20%  Final Exam30%

5 Resources  Please refer to the teaching plan  World wide web, but don’t rely too much on Wikipedia!

6 Course Contents Please refer to the teaching plan

7 Project  The goal of the project is to develop a non-trivial application that will enable you to practice the concepts learnt in class. There will be two types of student project teams: Architect team that interview stakeholders and design the system Stakeholder team that provides the development team with their functional and quality requirements

8  Each team will have the chance to become stakeholder and architect at the same time. The team consists of three to four students with one of the students being a lead architect. The stakeholder team consists of three to four students that play people who have a stake in the system to be designed.

9  The students devise their own roles they want to play. In the early weeks, the stakeholders should be available for the engineer team to be interviewed about their ideas, concerns, and requirements about the system.

10  This project aims to cultivate team building and interpersonal communication skills among group members, which also includes peer evaluation.

11  Project is undertaken in groups [that consists of 3 to 4 students]  Students may propose any project title but must have permission from the Course Instructor. A proposed project must be authentic and has not been designed or implemented elsewhere, otherwise marks will not be allocated

12  A final presentation will be made at a project presentation, which will take place in week 14. These presentations will be assessed, and every member in a group must participate. All students are COMPULSORY to attend every presentation and encourage to actively participating in the Q&A session. The project report must be submitted to your instructor on the day of the presentation.

13  For designs, students are strongly encouraged to use appropriate CASE tools. Software Architect and Rational Rose tools are available in the faculty’s lab (Block B). You may refer to any OO books for designing using CASE tools. Any unknown notation of elements will be marked ZERO.

14 Project Deliverables You are expected to produce a system with the following document that contains:  Glossaries and acronyms  Roles of each member in the development and stakeholder team  System overview and objectives  Requirements specifications (functional and non-functional)  An architectural design  Constraints (technical, managerial, economic, political)  Risks and non-risks  Sensitivity points and trade-offs  Issues and problems  A project plan and schedule setting out milestones, resource usage and estimated costs.

15 Paper Review  Choose a paper dated from 2008 onwards  The paper must be in the field of software architectural design  Do your critical analysis to include your arguments and opinions  Present your proposal in improving/enhancing the work of the paper – problem statement, objectives, relevance, methodology, benefits/contributions, and your proposed enhancement

16 Others  Be punctual  Miss class – 2 the most  No extra assignment/quiz/test to improve grade  No usage of laptop/phone during lecture/class discussion or exercise  Every member in the group must have the opportunity to present/participate in the class  This class requires 70% of your effort!


Download ppt "SIM5113 - SOFTWARE ARCHITECTURE Instructor: Masrah Azrifah Azmi Murad, PhD Room: C2.11 Email: masrah.azrifah [at] gmail.com OR masrah [at] fsktm.upm.edu.my."

Similar presentations


Ads by Google