Lecture notes for B.Tech IV Year, II Semester Computer Science and Engineering, R15 curriculum, academic year 2018 - 19. The five-unit course covers conventional and modern software management, software economics and cost estimation, iterative life-cycle phases, process artifacts, model-based architecture, workflows, milestones, project planning, organizational responsibilities, process automation, and project control metrics. Includes course objectives, outcomes, textbook and reference lists, and review questions.
Free preview text
The first 5 pages, shown as text so search engines and readers can find this document.
Page 1
I
Software Project Management
[R15A0543]
LECTURE NOTES
B.TECH IV YEAR – II SEM(R15)
(2018-19)
DEPARTMENT OF
COMPUTER SCIENCE AND ENGINEERING
MALLA REDDY COLLEGE OF ENGINEERING &
TECHNOLOGY
(Autonomous Institution – UGC, Govt. of India)
Recognized under 2(f) and 12 (B) of UGC ACT 1956
(Affiliated to JNTUH, Hyderabad, Approved by AICTE - Accredited by NBA & NAAC – ‘A’ Grade - ISO 9001:2015 Certified)
Maisammaguda, Dhulapally (Post Via. Hakimpet), Secunderabad – 500100, Telangana State, India
Page 2
II
IV Year B. Tech. CSE – II Sem L T/P/D C
4 - /- / - 4
(R15A0543) SOFTWARE PROJECT MANAGEMENT
(Core Elective-VI)
Objectives:
Understanding the specific roles within a software organization as related to project and
process management
Understanding the basic infrastructure competences (e.g., process modeling and
measurement)
Understanding the basic steps of project planning, project management, quality assurance,
and process management and their relationships
UNIT-I
Conventional Software Management: The waterfall Model, Conventional Software
Management Performance,
Evolution of Software Economics: software Economics. Pragmatic Software Cost Estimation.
Improving Software Economics: Reducing Software Product Size, Improving Software
Processes, Improving Team Effectiveness, Improving Automation, Achieving Required Quality,
Peer Inspections.
UNIT-II
Conventional and Modern Software Management: Principles of Conventional Software
Engineering, Principles of Modern Software Management, Transitioning to an interactive
Process.
Life Cycle Phases: Engineering and Production Stages Inception, Elaboration, Construction,
Transition phases.
UNIT-III
Artifacts of the Process: The Artifact Sets. Management Artifacts, Engineering Artifacts,
Programmatic Artifacts.
Model Based Software Architectures: A Management Perspective and Technical Perspective.
UNIT-IV
Flows of the Process: Software Process Workflows. Inter Trans Workflows.
Checkpoints of the Process: Major Mile Stones, Minor Milestones, Periodic Status
Assessments.
Interactive Process Planning: Work Breakdown Structures, Planning Guidelines, Cost and
Schedule Estimating. Interaction Planning Process, Pragmatic Planning.
UNIT-V
Project Organizations and Responsibilities: Line-of-Business Organizations, Project
Organizations, and Evolution of Organizations.
Process Automation: Building Blocks, the Project Environment.
Project Control and Process Instrumentation: Server Care Metrics, Management Indicators,
Quality Indicators, Life Cycle Expectations Pragmatic Software
Page 3
III
TEXT BOOKS:
1. Walker Rayce, “Software Project Management”, 1998, PEA.
2. Henrey, “Software Project Management”, Pearson.
Reference Books:
1. Richard H.Thayer.” Software Engineering Project Management”, 1997, IEEE Computer
Society.
2. Shere K.D.: “Software Engineering and Management”, 1998, PHI.
3. S.A. Kelkar, “Software Project Management: A Concise Study”, PHI.
4. Hughes Cotterell, “Software Project Management”, 2e, TMH. 88 5. Kaeron Conway,
“Software Project Management from Concept to D
Outcomes:
At the end of the course, the student shall be able to:
Describe and determine the purpose and importance of project management from the
perspectives of planning, tracking and completion of project
Compare and differentiate organization structures and project structures.
Implement a project to manage project schedule, expenses and resource with the
application of suitable project management tools
Page 4
IV
INDEX
UNIT NO TOPIC PAGE NO
I
Conventional Software Management 01 - 06
Evolution of Software Economics 07 - 10
Improving Software Economics 10 - 18
II
Conventional and Modern Software Management 19 - 23
Life cycle phases 24 - 28
III
Artifacts of the process 29 – 39
Model based software architectures 40 – 42
IV
Work Flows of the process 43 – 47
Checkpoints of the process 48 – 52
Iterative Process Planning 52 – 60
V
Project Organizations and Responsibilities 61 – 63
Process Automation 64 – 69
Project Control and Process Instrumentation 69 - 75
Page 5
1
UNIT – I
Conventional Software Management: The waterfall model, conventional software Management performance.
Evolution of Software Economics: Software Economics, pragmatic software cost estimation.
Improving Software Economics: Reducing Software product size, improving software processes, improving team
effectiveness, improving automation, Achieving required quality, peer inspections.
1. Conventional software management
Conventional software management practices are sound in theory, but practice is still tied to archaic (outdated)
technology and techniques.
Conventional software economics provides a benchmark of performance for conventional software manage-
ment principles.
The best thing about software is its flexibility: It can be programmed to do almost anything.
The worst thing about software is also its flexibility: The "almost anything" characteristic has made it difficult
to plan, monitors, and control software development.
Three important analyses of the state of the software engineering industry are
1. Software development is still highly unpredictable. Only about 10% of software projects are
delivered successfully within initial budget and schedule estimates.
2. Management discipline is more of a discriminator in success or failure than are technology advances.
3. The level of software scrap and rework is indicative of an immature process.
All three analyses reached the same general conclusion: The success rate for software projects is very low.
The three analyses provide a good introduction to the magnitude of the software problem and the current
norms for conventional software management performance.
1.1 THE WATERFALL MODEL
Most software engineering texts present the waterfall model as the source of the "conventional" software
process.
1.1.1 IN THEORY
It provides an insightful and concise summary of conventional software management
Three main primary points are
1. There are two essential steps common to the development of computer programs: analysis and
coding.
Waterfall Model part 1: The two basic steps to building a program.
2. In order to manage and control all of the intellectual freedom associated with software development,
one must introduce several other "overhead" steps, including system requirements definition,
software requirements definition, program design, and testing. These steps supplement the analysis
and coding steps. Below Figure illustrates the resulting project profile and the basic steps in
developing a large-scale program.
Analysis and coding both involve creative work that
directly contributes to the usefulness of the end product.
Analysis
Coding
This guide helps you understand the scope of Software Project Management [R15A0543] - Lecture Notes before or alongside reading the original document. It is based on the catalogue record, credited creator, source, classification and topics shown on this page. It does not replace the original work and does not invent claims about passages that Doxxly cannot verify.
Summary and overview
Software Project Management [R15A0543] - Lecture Notes is a 79-page documentcredited to Yusuf M. Quinlan. Lecture notes for B.Tech IV Year, II Semester Computer Science and Engineering, R15 curriculum, academic year 2018 - 19. The five-unit course covers conventional and modern software management, software economics and cost estimation, iterative life-cycle phases, process artifacts, model-based architecture, workflows, milestones, project planning, organizational responsibilities, process automation, and project control metrics. Includes course objectives, outcomes, textbook and reference lists, and review questions. It appears in the Technology & Security collection, which groups it with other material that readers may use for comparison and further study.
The item can be approached in several ways. A reader looking for a quick orientation can begin with the free five-page preview, inspect the page structure and use the metadata to judge relevance. Someone undertaking deeper research can work through the complete file, search its indexed text, record useful page references and compare its treatment of Software Project Management, Lecture Notes, B.Tech, Computer Science and Engineering, Software Economics, Iterative Development, Software Architecture, Project Planning, Process Automation, Software Metrics with the related resources linked below.
Rather than reducing the work to a single claim, this page treats it as a source that should be read in context. The title, creator, publication source, licence and format all help explain what kind of evidence it may offer. Readers should distinguish the original author's statements from Doxxly's catalogue description, and should cite the original edition when using the material in academic, professional or published work.
Key topics and reader takeaways
The catalogue connects this document with Software Project Management, Lecture Notes, B.Tech, Computer Science and Engineering, Software Economics, Iterative Development, Software Architecture, Project Planning, Process Automation, Software Metrics. These terms offer practical entry points rather than a substitute for close reading. Start by identifying the definitions, examples, arguments, tables or visual explanations attached to each topic. Then note where the creator draws connections, makes distinctions or moves from background material to a conclusion, recommendation, calculation or narrative development.
A useful reading method is to separate description from interpretation. First record what the item actually presents: names, headings, figures, formulas, quotations or stated propositions. Next consider why those details matter within the whole work. Finally compare them with another source from the same subject area. This process helps turn a long digital file into evidence that can be evaluated rather than merely skimmed.
Table of contents and reading guide
The following is an editorial content guide based on the verified catalogue topics. It is not represented as the original author's formal table of contents. Use it to organise notes while moving through the 79 pages in the player.
Part 1
Software Project Management
Use this section of the reading guide to identify how Software Project Management appears in Software Project Management [R15A0543] - Lecture Notes, note important terms, and connect the subject to the wider purpose of the work.
Part 2
Lecture Notes
Use this section of the reading guide to identify how Lecture Notes appears in Software Project Management [R15A0543] - Lecture Notes, note important terms, and connect the subject to the wider purpose of the work.
Part 3
B.Tech
Use this section of the reading guide to identify how B.Tech appears in Software Project Management [R15A0543] - Lecture Notes, note important terms, and connect the subject to the wider purpose of the work.
Part 4
Computer Science and Engineering
Use this section of the reading guide to identify how Computer Science and Engineering appears in Software Project Management [R15A0543] - Lecture Notes, note important terms, and connect the subject to the wider purpose of the work.
Part 5
Software Economics
Use this section of the reading guide to identify how Software Economics appears in Software Project Management [R15A0543] - Lecture Notes, note important terms, and connect the subject to the wider purpose of the work.
Part 6
Iterative Development
Use this section of the reading guide to identify how Iterative Development appears in Software Project Management [R15A0543] - Lecture Notes, note important terms, and connect the subject to the wider purpose of the work.
Part 7
Software Architecture
Use this section of the reading guide to identify how Software Architecture appears in Software Project Management [R15A0543] - Lecture Notes, note important terms, and connect the subject to the wider purpose of the work.
Part 8
Project Planning
Use this section of the reading guide to identify how Project Planning appears in Software Project Management [R15A0543] - Lecture Notes, note important terms, and connect the subject to the wider purpose of the work.
When a heading in the original differs from this guide, follow the original heading in your citation. Page numbers can also vary between editions. Doxxly's direct page field is useful for navigation, but formal references should include the title, creator, source and edition details available in the file itself.
About Yusuf M. Quinlan
Doxxly credits Yusuf M. Quinlan as the author or creator of Software Project Management [R15A0543] - Lecture Notes. This page does not add an unverified biography, job title or institutional affiliation. The attribution is preserved so readers can distinguish the creator from the hosting library and follow the original record when an external author link is available.
Author context matters because a work reflects a particular purpose, audience and point of view. Before relying on the material, consider what the creator set out to explain, when the source was produced and whether later research or revised guidance should also be consulted. For literature and philosophy, compare translations and editions; for technical material, check whether a newer version has superseded the one shown here.
About the source organisation
The recorded source for this item is mrcet.com. Doxxly provides access and discovery tools but does not claim to be the original publisher unless explicitly stated. Source links, creator attribution and the recorded Publicly available file collected for editorial review licence are displayed to help readers assess provenance and permitted use.
Provenance is especially important for reports, standards, presentations and working spreadsheets. Check the original source for amendments, supporting files and current policy. A trustworthy research workflow keeps the source URL with any notes or downloaded copy, verifies important figures against the original, and avoids treating an archived document as automatically current.
Begin with the title and opening pages, then use the guide above to decide whether to read sequentially or move to a particular topic. The Doxxly player provides previous and next navigation, a direct page field, zoom steps, fit-to-width and fit-to-page modes, rotation and fullscreen. These controls are useful when a page contains small type, a wide table, an image, a scanned layout or a dense sequence of notes.
The first five pages are open to every visitor. A plan unlocks the complete item and full-document search. Search is best used for distinctive names, technical terms or short phrases; broad words can produce too many possible contexts. When you find a useful passage, read the surrounding pages so that a sentence, chart or formula is not separated from its explanation.
If downloading is enabled, members can obtain the original PDF file. Keep the original format when formulas, slide sequencing, pagination or layout carries meaning. Respect the Publicly available file collected for editorial review terms displayed on this page, and use the rights-report link if you believe the attribution or availability needs review.
Research questions to consider
As you read Software Project Management [R15A0543] - Lecture Notes, ask which audience the creator addresses, what problem or idea organises the work, what evidence is presented, and which assumptions remain unstated. Note whether important terms are defined consistently and whether examples represent a broader pattern or a narrow case. For quantitative material, record units, time periods, formulas and data sources. For interpretive material, separate the creator's language from your own summary.
A second set of questions concerns relevance today. Which parts remain durable, which depend on their historical or institutional setting, and what would need confirmation from a newer source? Following the tags and the Technology & Security collection can reveal useful comparisons. Agreement between sources can strengthen confidence, while disagreement can point to changing definitions, methods, evidence or priorities.
Finally, decide what you need from the item: background knowledge, a quotation, a worked example, a model, a visual explanation or a starting bibliography. That purpose should guide the depth of reading and the notes you keep. Doxxly helps locate and navigate the source; careful interpretation remains the reader's responsibility.