Presentation is loading. Please wait.

Presentation is loading. Please wait.

Informatics 43 Discussion 13 May, 2016

Similar presentations


Presentation on theme: "Informatics 43 Discussion 13 May, 2016"— Presentation transcript:

1 Informatics 43 Discussion 13 May, 2016
MidTerm 2 Review Informatics 43 Discussion 13 May, 2016

2 MidTerm 2 Question List

3 Describe defining characteristics of open source software development.

4 Characteristics of Open Source Software Development
Software made available, for free, in executable form, access to source provided Small releases- Frequent (Few months to few years) Informal, written communication using Internet tools Customer Availability- Developers are initial customers Continuous Integration through Internet tools Requirements may change, collected informally Informal and iterative design Minimal documentation- relies on source code Possibly large distributed teams Scaling

5 The Mythical Man-Month, to help you as a junior member
How could you use Brooks’ Law, from The Mythical Man-Month, to help you as a junior member of a software development team?

6 Causes for scheduling disasters
We expect that all will go well. We confuse effort with progress, and think that people and months are interchangeable. Managers are often insufficiently stubborn. Schedule progress is poorly monitored. When schedule slippage is recognized, more people are added.

7 Brooks’s Law: Adding manpower to a late software project
makes it later.

8 You are a Junior Developer

9 values of the “agile” approach to software development are violated by
Which, if any, values of the “agile” approach to software development are violated by the Waterfall Model?

10 Values of Agile Approach violated by Waterfall Model
User Involvement Agile -needs users to be involved to provide constant feedback Waterfall- Limited interaction with users- only requirements phase & delivery Documentation Agile- Minimal Waterfall- Heavy (requirements, design & testing) Short releases and Iteration Incremental Design

11 Draw a UML Class Diagram for WebReg.

12 Requirements for WebReg
You may use WebReg to enroll in classes and make schedule changes during both the Enrollment by Window and Open Enrollment periods. Once logged in to WebReg, you will be able to: Add a class (through 2nd week of instruction) Drop a class (through 2nd week of instruction) Change the grading option of a class (through 2nd week of instruction) Change the unit value of a variable unit course (through 2nd week of instruction) Use the waitlist option until waitlists are deactivated View co-classes List the open sections of selected classes Receive confirmation of successful enrollment transactions Receive error messages for unsuccessful attempts to add, drop, or change enrollment Be notified of any academic holds on your record Verify your registration fee status As an undergraduate, you may enroll in as few as 12.0 units or as many as 20.0 units per quarter. However, undergraduate enrollment will be limited to 18.0 units until WebReg reopens after the fee payment deadline. The status of a course indicates the seat availability in that particular course. A UCInetID and password is required to use WebReg. These requirements may be more complex than what you know about WebReg. Make the class diagram as per what the question mentions, and what you know with respect to it.


Download ppt "Informatics 43 Discussion 13 May, 2016"

Similar presentations


Ads by Google