01intro_b - 01 Intro, part B 17 Jan 2011 CSCD08S Software...

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

View Full Document Right Arrow Icon
01 Intro, part B 17 Jan 2011 CSCD08 Software Engineering 1 01 Intro, part B CSCD08 Software Engineering 1 CSCD08S Software Engineering Introduction: Large Software Systems, Notable Failures, Importance and Goals of SE
Background image of page 1

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

View Full DocumentRight Arrow Icon
01 Intro, part B 17 Jan 2011 CSCD08 Software Engineering 2 01 Intro, part B CSCD08 Software Engineering 3 Course Perspective on SE b Software product company, not: h IT department h Consulting company (e.g. Accenture, McKinsey) h Service organization (e.g. IBM services) h note a software product company may still have these others as sub-departments b May seem too abstract to be interesting, but useful to consider what SE roles appeal to you and to be aware of how those roles intersect with the roles of other people/parts of the company. b What are these “roles”? To name a few: h Developer, architect, professional services, project management, product management, sales engineer, SQA, management s.a. team lead, manager, director h Roles may span function, e.g. development tasks required for building product, SQA, professional services, even sales engineering
Background image of page 2
01 Intro, part B 17 Jan 2011 CSCD08 Software Engineering 3 01 Intro, part B CSCD08 Software Engineering 7 Real s/w Systems resemble Puzzles b The dimensionality of the puzzle (connections between pieces) is much higher that can be shown on a 2-dimensional slide. b Each piece may be written by different (group of) programmers. b Each piece has a rigorously specified interface that describes how it interconnects with other pieces. b For a program to be correct, all of the pieces must fit exactly. b The shape of the pieces and the interconnections between them change over time as the program is modified and maintained.
Background image of page 3

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

View Full DocumentRight Arrow Icon
01 Intro, part B 17 Jan 2011 CSCD08 Software Engineering 4 01 Intro, part B CSCD08 Software Engineering 8 1,000,000 lines of source code => • 16.7 hours to compile at 1000 lines/minute (wildly optimistic) • hard copy: 13,333 pages at 75 lines/page (laser print) giving you a 4’5” high stack of paper (500 pg/2”) that takes 22.2 hours to print at 10 pgs/minute • soft copy: 41,667 screens at 24/lines/screen or 20,833 screens at 48 lines/screen many real software systems are 3 . . 6,000,000 lines of source code some existing systems are in the 10 . . 20,000,000 range Windows XP is alleged to be more than 40,000,000 lines Linux 7.1 distribution contains over 30,000,000 lines of source code Mac OS/X 10.4 reputed to consist of more than 85,000,000 lines Calibration on LARGE
Background image of page 4
17 Jan 2011 CSCD08 Software Engineering 5 01 Intro, part B CSCD08 Software Engineering 9 How is Large Software “Different”? b Scale: h precludes total comprehension by any individual b Complexity: h number of classes, functions, control-flow paths b Continuing Change: h during specification, design, implementation and throughout lifetime. b
Background image of page 5

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

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

Page1 / 34

01intro_b - 01 Intro, part B 17 Jan 2011 CSCD08S Software...

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

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