CSE 360 Exam 1 Arizona State University Questions
And Answers Real Tests
Software - 1 ANS instructions (computer programs) that when executed provide desired features, function,
and performance
Software - 2 ANS data structures that enable the programs to adequately manipulate information
Software - 3 ANS documentation that describes the operation and use of the programs
"Software Engineering" Origin ANS 1968 - Fortran, assembly, etc.: limited, problems were diff - no
phones; no OOP
1968 NATO Conference, Garmisch, Germany
Aim:
3 Problems:
Current Situation: ANS Aim: To solve the software crisis
Problem Identified: Software is delivered
Late
Over budget
With residual faults - still had errors in code
2018: Problems still exist although/because computers are very diff
2006 Standish Group Data ANS 19% canceled
35% successful
46& late, over budget, and/or missing features
Current Situation of Software Crisis ANS Not resolved
Moving target
"Software Depression" = long duration + poor prognosis
,Software Engineering Importance ANS ALL developed nations' economies depend on software
Controls more and more systems
Software expenditure = sig fraction of GNP of all developed nations
Software Engineering Definition ANS 1) application of a systematic-reproducible, disciplined-set
protocols, quantifiable-measurable approach to the development, operation-use, and maintenance-
improvement/changes over its life of software; that is, the application of engineering-been around for a long
time- to software
2) The study of approaches as in (1).
Software Engineering Overview ANS all aspects of software production: specification to maintenance until
phased out
Appropriate theories w.in org and financial constraints
Project management, tool dev, methods, etc. to support software production
Software Engineering Benefits ANS reliable, economical, efficient, feasible
increasing reliance => need trustworthy, fast systems
cheaper in long run to use SWE methods
most costs = changing sw after gone into use
Don't practice as students
SW Project Failure ANS Due to increasing system complexity
Larger, more complex systems -> demands change
Customer base requires quick solutions for larger and more complex problems
New capabilities previously thought impossible
Software Different? ANS Developed/engineered rather than manufactured
Doesn't "wear out" given computer and supporting system
Moving toward component-based construction = "take off shelf" - most sw is custom-built
"Good" SW ANS Maintainability
Dependability
, Efficiency
Acceptability
Maintainability ANS cost stems from here
Dependability ANS accurate and secure from unwanted changes
Efficiency ANS functional while minimizing CPU and mem use
Acceptability ANS meet customer specifications
Common SW Activities ANS SW Specification
SW Development
SW Validation
SW Evolution
SW Specification ANS customers and engineers define sw to be produced + constraints on operation
SW Development ANS sw is designed and programmed: coding + testing (mostly at unit level)
SW Validation ANS sw is checked to ensure is acceptable
SW Evolution ANS sw modified to reflect customers' changing and market reqs
bug fixes, new system and functionalities
SW Engineering Diversity: 2 Types of SW Systems ANS Stand-alone
Interact w/ other systems
SW Engineering Diversity ANS No universal set of sw techniques applicable to all sw systems due to diff
req
And Answers Real Tests
Software - 1 ANS instructions (computer programs) that when executed provide desired features, function,
and performance
Software - 2 ANS data structures that enable the programs to adequately manipulate information
Software - 3 ANS documentation that describes the operation and use of the programs
"Software Engineering" Origin ANS 1968 - Fortran, assembly, etc.: limited, problems were diff - no
phones; no OOP
1968 NATO Conference, Garmisch, Germany
Aim:
3 Problems:
Current Situation: ANS Aim: To solve the software crisis
Problem Identified: Software is delivered
Late
Over budget
With residual faults - still had errors in code
2018: Problems still exist although/because computers are very diff
2006 Standish Group Data ANS 19% canceled
35% successful
46& late, over budget, and/or missing features
Current Situation of Software Crisis ANS Not resolved
Moving target
"Software Depression" = long duration + poor prognosis
,Software Engineering Importance ANS ALL developed nations' economies depend on software
Controls more and more systems
Software expenditure = sig fraction of GNP of all developed nations
Software Engineering Definition ANS 1) application of a systematic-reproducible, disciplined-set
protocols, quantifiable-measurable approach to the development, operation-use, and maintenance-
improvement/changes over its life of software; that is, the application of engineering-been around for a long
time- to software
2) The study of approaches as in (1).
Software Engineering Overview ANS all aspects of software production: specification to maintenance until
phased out
Appropriate theories w.in org and financial constraints
Project management, tool dev, methods, etc. to support software production
Software Engineering Benefits ANS reliable, economical, efficient, feasible
increasing reliance => need trustworthy, fast systems
cheaper in long run to use SWE methods
most costs = changing sw after gone into use
Don't practice as students
SW Project Failure ANS Due to increasing system complexity
Larger, more complex systems -> demands change
Customer base requires quick solutions for larger and more complex problems
New capabilities previously thought impossible
Software Different? ANS Developed/engineered rather than manufactured
Doesn't "wear out" given computer and supporting system
Moving toward component-based construction = "take off shelf" - most sw is custom-built
"Good" SW ANS Maintainability
Dependability
, Efficiency
Acceptability
Maintainability ANS cost stems from here
Dependability ANS accurate and secure from unwanted changes
Efficiency ANS functional while minimizing CPU and mem use
Acceptability ANS meet customer specifications
Common SW Activities ANS SW Specification
SW Development
SW Validation
SW Evolution
SW Specification ANS customers and engineers define sw to be produced + constraints on operation
SW Development ANS sw is designed and programmed: coding + testing (mostly at unit level)
SW Validation ANS sw is checked to ensure is acceptable
SW Evolution ANS sw modified to reflect customers' changing and market reqs
bug fixes, new system and functionalities
SW Engineering Diversity: 2 Types of SW Systems ANS Stand-alone
Interact w/ other systems
SW Engineering Diversity ANS No universal set of sw techniques applicable to all sw systems due to diff
req
