CIDM 4390 Midterm Topics

CIDM 4390 Midterm Topics - O verarching Caveat A ll answers...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon
Overarching Caveat – All answers must be related to the particulars and details of your own team’s project. Discussion Leadership Assignments Week  Assignment 4 - 02/06 to 02/12 Mercury - Chapter 4 Jupiter - Chapter 5 05 – 02/13 to 02/19 Mercury - Chapter 12 Jupiter - Chapters 8 and 9 06 – 02/20 to 02/26 Mercury - Chapter 6 Jupiter - Chapter 7 07 – 02/27 to 03/05 Mercury - Chapter 17 Jupiter - Chapter 14, 15 and 16 09 – 03/20 to 03/26 Mercury - Chapter 13 Jupiter - Chapter 10 and 11
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
10 – 03/27 to 04/02 Mercury - Chapter 20 11 – 04/03 to 04/09 Jupiter - Chapter 29 Chapter One – Software Software Engineering : Explain the 4 layers of software engineering: tools, methods, process, quality (pg 13-14) o Total quality management leads to the development of increasingly more effective approaches to software engineering. Any engineering approach must rest on an organizational commitment to quality. o Process in software engineering is the glue that holds the technology layers together. Process defines a framework that must be established for effective delivery. The software process forms the basis for management control of software projects. Team Jupiter is currently using the Rational Unified Process as a means to define our framework. o Methods provide the technical how-to’s for building software. They encompass a broad array of tasks such as communication, testing, design modeling, ect. Methods include modeling activities and other descriptive techniques. o Tools provide automated or semi automated support for the process and the methods. Jupiter is using tools by using Sharepoint to communicate, Visual studio to test, and IBM rational for design modeling. ***Seven Principles : What are Pressman’s 7 principles? (Pg 19-21) o The reason it all exists: all software exists to provide value to its users. All decisions should be made with this in mind. If the decision doesn’t provide value, it shouldn’t be done.
Background image of page 2
o Keep it Simple, stupid: All design should be a simple as it can be, but no simpler. This allows for a more easily understood and easily maintained system. This makes software more maintainable and less error-prone. o Maintain the vision: A clear vision is essential to the success of a software project. Without one, a project almost unfailingly ends up being “of two minds” about itself. Compromising the architectural vision weakens and will eventually break even the well designed systems. o What you produce, others will consume: It is important to design while keeping others in mind. Someone else will eventually have to be in charge of using, maintaining, documenting, or depend on being able to understand the system. Making someone else’s job easier adds value to the system. o
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 4
This is the end of the preview. Sign up to access the rest of the document.

This document was uploaded on 04/09/2011.

Page1 / 12

CIDM 4390 Midterm Topics - O verarching Caveat A ll answers...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online