New User Special Price Expires in

Let's log you in.

Sign in with Facebook


Don't have a StudySoup account? Create one here!


Create a StudySoup account

Be part of our community, it's free to join!

Sign up with Facebook


Create your account
By creating an account you agree to StudySoup's terms and conditions and privacy policy

Already have a StudySoup account? Login here

Software Engineering, Week 2 Notes

by: Judy

Software Engineering, Week 2 Notes CSC4110

Marketplace > Wayne State University > Computer science > CSC4110 > Software Engineering Week 2 Notes
GPA 3.64

Preview These Notes for FREE

Get a free preview of these Notes, just enter your email below.

Unlock Preview
Unlock Preview

Preview these materials now for free

Why put in your email? Get access to more of this material and other relevant free materials for your school

View Preview

About this Document

Chapters 1 and 2. Topics include: History of Software Difficulties Programmers Face Essential Difficulties Software Engineering The beginning of software engineering Paradigm Anomaly Par...
Software Engineering
Vaclav Rajlich
Class Notes
software, Engineering, paradigm, Lifespan
25 ?




Popular in Software Engineering

Popular in Computer science

This 3 page Class Notes was uploaded by Judy on Friday September 9, 2016. The Class Notes belongs to CSC4110 at Wayne State University taught by Vaclav Rajlich in Fall 2016. Since its upload, it has received 7 views. For similar materials see Software Engineering in Computer science at Wayne State University.


Reviews for Software Engineering, Week 2 Notes


Report this Material


What is Karma?


Karma is the currency of StudySoup.

You can buy or earn more Karma at anytime and redeem it for class notes, study guides, flashcards, and more!

Date Created: 09/09/16
OneNote Online Week 2 Notes Tuesday, September 06, 201610:23 PM History of Software Software is everywhere People who develop software possess the tools and skills to allow them to develop and evolve software Difficulties Programmers Face Accidental Current, past and future technology Quirks of the OS, compilers, languages, processes These tend to come and go Essential Subset of the defining properties There are no easy answers to these Essential Difficulties Invisibility Senses are not easily used in comprehension Visualization and sonification requires a lot of work Complexity Programs are among the most complex systems out there Our short term memory only accommodates approx. 7 things at a time Changeability Software is constantly changing Yesterday's comprehension may be obsolete today Conformity Programs glue the large system all together, and reflects said large system This adds to the complexity Discontinuity People are able to easily understand linear and semi-linear systems (continuous) Discontinuity is  when a small change of input can result in a large change in the output Software Engineering A set of recommendations of how to develop software A discipline with lots of knowledge The beginning of Software Engineering Software separated from Hardware in the 1950s Original programmers were recruited from current hardware engineers and mathematicians who used their ad-hoc methods from their former fields Paradigm A coherent tradition of scientific research (definition) Consists of not only the ideas, but also the investment Currently an overused terms Anomaly An important fact that directly contradicts the old paradigm Dilemma: To disregard the anomaly or to shift paradigms To shift is to abandon the large investment in the old paradigm The anomaly must be compelling enough to make a shift seem like the better option Paradigm Shift Discontinuity in the development of a discipline (a revolution) Paradigm shift of 1970 Established the discipline of software development Dealt with the complexity and made design an important consideration Introduced the waterfall metaphor Waterfall Metaphor Good design avoids expensive work later Became the dominant paradigm in the past  A major contributor to software cost Waterfall Paradigm Has elaborate up front activities (Big Design Up Front) 1 of 3 09/09/2016 07:58 PM OneNote Online Textbooks are still largely based on waterfall Anomaly of Requirements Volatility 30% or more of initial requirements can change during development Standish Group Anomaly Waterfall did not solve the problems of software development Many projects were cancelled, only 16% were considered successful Band-Aid's Prototyping - problem is that volatility continues after the prototype is developed All three of the paradigms currently coexist 1.Ad-hoc where software development is more of an art than engineering 2.Waterfall, which works if there is no volatility 3.Evolutionary paradigm which is currently mainstream 9/8/2016 CHAPTER 2 – Lifespan Models The stages that software goes through from life to death Software is a product, and it follows a similar lifespan though some stages may be different Product Lifespan Introduction -> Growth -> Maturity -> Decline Software Lifespan Unique proprietary software follows the same curve, though the stage names are different Staged Model 1.Initial Development: The first version of the software is introduced 2.Evolution: Evolution changes the software up until it stops 3.Servicing/Maintenance: Patches are released for the software until it stops 4.Phase Out: The software goes into decline until it is switched off, maintenance stops 5.Close Down: Software is obsolete Initial Development Includes requirements, design, and implementation Fundamental decisions are made in regards to technology, architecture, and program domain knowledge Evolution Adapting the software to user operations and environment Adding new features, correcting mistakes, responding to learning and changes in technology The software usually grows during this time Software architecture and team knowledge make evolution possible Evolution Stops Can be cause by a managerial decision, software stabilization or code decay Code Decay Loss of software coherence, software knowledge, key personnel Challenge of software development is to slow down or eliminate code decay Servicing/Maintenance No additions to functionality are made Changes are limited to patches and wrappers The process is very different from evolution There is no need for senior engineers The process is very predictable Reversal from servicing This is expensive and rare It is not simply a technical problem, but software team knowledge must be recovered Reengineering Uses the same model but servicing goes back to the evolution stage Phase Out No more servicing is being undertaken Users must work around the  deficiencies 2 of 3 09/09/2016 07:58 PM OneNote Online Close Down Software use is disconnected Users are directed toward a replacement An exit strategy is needed Versioned Staged Model Used by software with many users Versions of the software are released in stages rather than all at once Incomplete Lifespan Often happens with discontinued projects, stable domains (waterfall)  Development can sometimes start with evolution Lifecycle vs Lifespan There is no cycle, so lifecycle is technically incorrect Lifespan is better terminology V model Modified waterfall, looks like a V Left branch follows same as waterfall Right branch is the testing and maintenance Prototyping Model Requirements -> Prototype -> Corrected requirements -> Design -> Implementation -> maintenance Attempts to prevent volatility 3 of 3 09/09/2016 07:58 PM


Buy Material

Are you sure you want to buy this material for

25 Karma

Buy Material

BOOM! Enjoy Your Free Notes!

We've added these Notes to your profile, click here to view them now.


You're already Subscribed!

Looks like you've already subscribed to StudySoup, you won't need to purchase another subscription to get this material. To access this material simply click 'View Full Document'

Why people love StudySoup

Steve Martinelli UC Los Angeles

"There's no way I would have passed my Organic Chemistry class this semester without the notes and study guides I got from StudySoup."

Anthony Lee UC Santa Barbara

"I bought an awesome study guide, which helped me get an A in my Math 34B class this quarter!"

Bentley McCaw University of Florida

"I was shooting for a perfect 4.0 GPA this semester. Having StudySoup as a study aid was critical to helping me achieve my goal...and I nailed it!"


"Their 'Elite Notetakers' are making over $1,200/month in sales by creating high quality content that helps their classmates in a time of need."

Become an Elite Notetaker and start selling your notes online!

Refund Policy


All subscriptions to StudySoup are paid in full at the time of subscribing. To change your credit card information or to cancel your subscription, go to "Edit Settings". All credit card information will be available there. If you should decide to cancel your subscription, it will continue to be valid until the next payment period, as all payments for the current period were made in advance. For special circumstances, please email


StudySoup has more than 1 million course-specific study resources to help students study smarter. If you’re having trouble finding what you’re looking for, our customer support team can help you find what you need! Feel free to contact them here:

Recurring Subscriptions: If you have canceled your recurring subscription on the day of renewal and have not downloaded any documents, you may request a refund by submitting an email to

Satisfaction Guarantee: If you’re not satisfied with your subscription, you can contact us for further help. Contact must be made within 3 business days of your subscription purchase and your refund request will be subject for review.

Please Note: Refunds can never be provided more than 30 days after the initial purchase date regardless of your activity on the site.