click below
click below
Normal Size Small Size show me how
COS397 Q1
| Question | Answer |
|---|---|
| 3 types of stones | Keystone, Cornerstone, Capstone |
| Capstone | Is at the very top above keystone |
| Keystone | At the top of the arch |
| Cornerstone | In the bottom corner |
| Brooks project time spent breakdown | 1/6 coding 1/3 planning 1/4 component and early system test 1/4 system test |
| What is Brook's law? | |
| Why is the Man-month mythical? | |
| What are the 10 primary elements of success in the CHAOS report | 1. User Involvement 2. Executive Management Support 3. Clear Statement of Requirements 4. Proper Planning 5. Realistic Expectations 6. Smaller Project Milestones 7. Competent Staff 8. Ownership 9. Clear Vision & Objectives 10. Hard-working staff |
| Somerville project time breakdown | 60% development 40% testing |
| Platinum Rule | Treat others as they want to be treated |
| 4 Personality Types | Dominant, Influencing, Steady, Conscientious |
| Goleman: What is EQ (5) | Self Awareness Managing Emotions Self-Motivation Empathy Handling Relationships |
| Conscientious (perfect) needs | Space, Sense of Order |
| Dominant (powerful) needs | Control |
| Steady (peaceful) needs | Feeling of worth |
| Influencing (Popular) needs | Attention, Approval |
| What is Dunning-Kruger graph | People who know nothing tend to have very high confidence |
| Dunning-Kruger Axis | Confidence (y), Wisdom (x) |
| SDLC | Software Development Life Cycle |
| SDLC Definition | Blueprints for development, testing, deployment and Maintenace of software. |
| V-Model | |
| Pigs | Product Owner, Team, Scrum Master |
| Chickens | Project Management, Project Assurance, Managers, Stakeholders |
| Incremental Model | |
| Waterfall | |
| Spiral | |
| Agile | |
| Iterative | |
| Agile Manifesto | Individuals and Interactions Working Software Customer Collaboration Responding to Change |
| Product Owner | Represents the stakeholders and is the voice of the customer |
| Scrum Master | Coaching., Helping, Assisting team |
| Extreme Programming (XP) | Pair Programming Refactoring |
| YAGNI Approach is a part of what process | Extreme Programming |
| Rational Unified Process (IBM) | Derived from work on the UML and associated process |
| What is a requirement | A specification of what is desired |
| Software Engineers perspective on requirements | What needs to be implemented What properties to be tested |
| Requirement Process | Elicitation, Analysis, Specification, Management, |
| Requirements tell you: | What you're doing When you're done |
| 2 Reasons software programs fail | Poor requirements Poor management |