21CS61 21CS61

Model Question Paper-1/2 with effect from 2021(CBCS Scheme) quality, the deliverables of successful projects, and the
necessity of documentation in software engineering.
US 5. The impact of software requirements changes varies with
N timing, with early changes incurring lower costs.
Sixth Semester B.E. Degree Examination Software 6. The misconception that software engineering leads to
Engineering and Project Management
voluminous and unnecessary documentation is debunked,
emphasizing the focus on creating a quality product.
TIME: 03 Hours SET - 3 Max. Marks: 7. A prevalent myth among software practitioners is the
100 belief that the job is done once the program is working,
while industry data shows ongoing efforts post-delivery.
Note:01.Answer any FIVE full questions, choosing at least ONE question from each MODULE. 8. Effective software quality assurance mechanisms like
THESE ANSWERS FROM TEXTBOOK technical reviews are crucial from the project's inception.

b Briefly explain Concurrent models and Specialized L2 CO1 10

Bloom ’s COs
Module -1 Taxonomy Marks
Process Models
DOWNLOAD Level
. Brief Explanation of Concurrent Models and Specialized
Q.01 a Software has characteristics that are considerably different L2 CO1 10 Process Models
than those of
hardware. Justify. Also Explain various software myths. Concurrent Models
Concurrent modeling in software development allows for
Characteristics of Software vs. Hardware and Software iterative and concurrent elements to be represented across
Myths various process models. It involves triggering transitions
based on events among different software engineering
Characteristics of Software vs. Hardware: activities simultaneously. For instance, modeling activities
1. Software is intangible and can't wear out like hardware can transition between states based on events triggered
does over time due to environmental factors. during the design phase. Concurrent modeling is applicable
2. Software costs are concentrated in engineering compared to all software development types and provides a
to hardware projects. comprehensive view of project states through a process
3. Software can be quickly modified and updated compared network, allowing for simultaneous existence of multiple
to hardware changes. activities.
4. Software requires intense thought and adherence to
specific principles for successful development. Specialized Process Models
5. Software defects can lead to high failure rates early in Specialized process models are utilized when a specific or
the program's life but can be corrected with updates. narrowly defined software engineering approach is chosen.
6. Software development depends heavily on effective and These models typically incorporate characteristics from
continuous communication between customers and traditional models but are tailored to specific project
developers. requirements. An example of a specialized process model is
Component-Based Development, where software is built
Software Myths: using pre-defined components that can be integrated to
1. Myths about software stem from erroneous beliefs about create complex systems efficiently.
the software development process.
2. Software myths often appear reasonable, intuitive, and
are perpetuated by experienced practitioners.
3. Examples of software myths include beliefs about
standards and procedures, schedule management, and the OR
impact of adding more programmers.
4. Some myths revolve around the assessment of software
Page 01 of 02 Page 01 of 02
07082024 07082024
 21CS61 21CS61
Q.02 a Explain the Incremental Development Process model L2 CO1 10 increment serves as a platform for user evaluation and
with a neat diagram. Also, mention the benefits of this feedback, leading to continuous improvement in
model compared to the waterfall model. subsequent iterations.
7. Adaptability to Business Deadlines : Incremental
Incremental Development Process Model and Benefits development can align with business deadlines by
compared to Waterfall Model delivering core functionalities early and adding
supplementary features progressively.
8. Enhanced User Involvement : Users can actively
participate in the development process through
incremental releases, fostering collaboration and ensuring
the product meets their needs effectively.

Diagram:
The incremental model applies linear sequences in a
staggered fashion as calendar time progresses, producing
deliverable increments of the software. The diagram
Incremental Development Process Model: visually represents how each increment adds functionality
The incremental process model focuses on delivering an over time, leading to the complete product.
operational product in increments. Early increments are
simplified versions of the final product that provide basic b Explain characteristics that differentiate WebApps from L2 CO1 10
functionality for user evaluation and serve as a platform other software
for future development. It is particularly useful when
staffing is limited, allowing for gradual implementation . Characteristics Differentiating WebApps from Other
based on user feedback and technical considerations. The Software
process involves iterative cycles of planning,
modification, and delivery of new features until the Network-Centric Nature
complete product is achieved. - WebApps are network-centric software applications
designed to serve a diverse community of clients.
Benefits of Incremental Model over Waterfall Model: - They reside on a network, providing worldwide or limited
1 . Flexibility : The incremental model accommodates access and communication.
changes and evolving requirements more effectively than - Must cater to varying patterns of usage among end users.
the rigid waterfall model.
2. Early Delivery of Functionality : Users receive basic User Load and Performance
functionality quickly with incremental releases, allowing - WebApps may experience unpredictable load , with
for early feedback and validation. the number of users varying significantly day by day.
3. Risk Management : Technical risks can be managed by - Concurrency is a key feature, allowing a large number of
planning increments to avoid dependencies or users to access the WebApp simultaneously.
uncertainties, ensuring timely delivery of partial - Performance is crucial, as delays may lead users to seek
functionalities. alternatives, emphasizing the importance of timely
4. Operational Product with Each Increment : Users can access .
benefit from operational products with each increment,
providing value early in the development process. Content Delivery and Aesthetics
5. Resource Optimization : Incremental development - WebApps primarily function to present text, graphics,
allows for flexibility in staffing, enabling the audio, and video content to users.
implementation of early increments with fewer resources - Content sensitivity is vital, influencing the overall
initially. quality and appeal of the WebApp.
6. Iterative Evaluation and Improvement : Each - Aesthetics play a significant role in the success of
WebApps, influencing user engagement and satisfaction.
Page 01 of 02 Page 01 of 02
07082024 07082024
 21CS61 21CS61
Module-2
DOWNLOAD
Continuous Evolution and Immediacy
- Unlike traditional software, WebApps evolve continuously
rather than through planned releases. Q. 03 a What are the basic guidelines for conducting a L2 CO2 10
- Immediacy is a defining characteristic, emphasizing collaborative requirements gathering meeting . Write a
short note on negotiating and validating requirements.
the swift deployment and updates of WebApps.
- Content updates can occur on a minute-by-minute basis,
reflecting the need for real-time adjustments and Basic Guidelines for Conducting a Collaborative
enhancements. Requirements Gathering Meeting

Security and Data-Driven Design Key Guidelines for Conducting a Collaborative

- Security is a critical concern due to network Requirements Gathering Meeting:
- Meetings should include both software engineers and other
accessibility, necessitating robust measures to
stakeholders.
protect sensitive content.
- WebApps often rely on data-driven design, accessing - Establish rules for preparation and participation.
- Formally suggest an agenda that covers all essential points
information from external databases for functionality and
but informally encourages the free flow of ideas.
content delivery.
- Appoint a facilitator to control the meeting.
Availability and User Demand - Utilize a "definition mechanism" such as work sheets, flip
- Users expect availability around the clock, with charts, or electronic platforms for collaboration.
demands for 24/7/365 access to popular WebApps.
- User demand can vary across different time zones, Negotiating and Validating Requirements:
- Negotiation involves determining the priority, availability,
highlighting the need for continuous service provision.
and relative cost of each requirement in collaboration with
Integration and Business Applications project stakeholders.
- WebApps are increasingly integrated with - The negotiation aims to develop a realistic project plan.
corporate databases and business applications , - Validation ensures that each requirement and the
requirements model align with customer needs to ensure the
expanding their functionality beyond standalone
-features.
They serve as sophisticated computing tools, bridging the right system is built.
gap between marketing, computing, and data transmission.
Additional Information on Collaborative Requirements
Gathering:
- Stakeholders work together to identify the problem,
propose solutions, negotiate approaches, and specify
solution requirements.
- Different approaches to collaborative requirements
gathering have been proposed, all following similar
fundamental guidelines.
- Mini-specifications are developed for entries on lists to
elaborate on objects or services, facilitating stakeholder
discussion and refinement.

Page 01 of 02 Page 01 of 02
07082024 07082024
 21CS61 21CS61
b Illustrate Scenario Based Modeling with Safe Home L3 CO2 10 condition encountered.
Surveillance - Priority: Moderate, to be implemented after basic
example. functions.
- Available in: Third increment.
Scenario Based Modeling with Safe Home Surveillance - Frequency of Use: Moderate.
- Channel to Actor: Via PC-based browser and
SafeHome Surveillance Functionality Internet connection.
- The SafeHome surveillance subsystem allows - Secondary Actors: System administrator, cameras.
homeowners to perform various functions such as selecting - Open Issues: Mechanisms to protect unauthorized
cameras, requesting thumbnails, displaying camera views, use by SafeHome employees.
controlling pan and zoom, recording output, and accessing
surveillance via the Internet. Use Case Details: System Activation
- Use cases are developed for each function identified, - InitiateMonitoring Use Case:
initially in an informal narrative style and later in a - Primary Actor: Homeowner
structured format for more formality. - Goal: Set system to monitor sensors when leaving or
staying inside
Example Scenario: Accessing Camera Surveillance via - Preconditions: System programmed with password
the Internet and sensor recognition
- Primary Actor: Homeowner - Trigger: Homeowner decides to activate alarm
- Goal: View camera output from anywhere via the functions
Internet - Scenario Steps: Observes control panel, enters
- Preconditions: System fully configured, valid user ID password, selects "stay" or "away," observes alarm light
and passwords obtained for system status.
- Trigger: Homeowner decides to check the house
remotely OR
- Scenario Steps: Q.04 a Explain Class-Responsibility-Collaborator (CRC) L2 CO2 10
1. Homeowner logs onto SafeHome Products website. Modeling and data modeling with an example
2. Enters user ID and two valid passwords.
3. System displays major function buttons. Class-Responsibility-Collaborator (CRC) Modeling and
4. Selects "surveillance" from the buttons.
5. Picks a camera from the floor plan.
6. System shows the house floor plan.
7. Selects a camera icon from the floor plan.
8. Selects the "view" button.
9. Viewing window displays camera output identified by
the camera ID.
10. Video output is displayed at one frame per second.

Exceptions and Additional Information

- Exceptions:
1. Incorrect or unrecognized ID/passwords - see use case
Validate ID and passwords.
2. Surveillance function not configured - system shows
error message, see use case Configure surveillance
function.
3. No floor plan or not configured - system displays error,
see use case Configure floor plan.
4. Alarm condition encountered - see use case Alarm Data Modeling Analysis
Page 01 of 02 Page 01 of 02
07082024 07082024
 21CS61 21CS61
b How can you develop an effective use case? Develop a L3 CO2 10
Class-Responsibility-Collaborator (CRC) Modeling UML use case
- CRC modeling is a method for identifying and organizing diagram for home security function.
relevant classes in a system or product based on
responsibilities and collaborations. Developing an Effective Use Case and UML Use Case
- Responsibilities refer to attributes and operations Diagram for Home Security Function
pertinent to a class, while collaborators are other classes
that interact with the main class. Developing an Effective Use Case:
- A CRC model consists of index cards with the class 1. A use case depicts the software or system from the end
name, responsibilities, and collaborators listed. user's point of view.
- The goal of CRC modeling is to provide an organized 2. Use cases focus on functional and behavioral
representation of classes to facilitate system understanding requirements, emphasizing interactions and tasks.
and design. 3. Use cases should be clear, detailed, and unambiguous to
effectively communicate requirements.
Data Modeling 4. Each use case should be reviewed carefully to ensure
- Data modeling describes the information space accuracy and completeness.
manipulated by software, beginning with data objects and 5. Consider all possible scenarios and exceptions to develop
their attributes. comprehensive use cases.
- Relationships between data objects are defined in data 6. Use cases can be narrative text, task outlines, template-
modeling to represent how they interact. based descriptions, or diagrams.
- Data modeling complements scenario-based and class- 7. Ambiguities in a use case can indicate underlying
based modeling to identify analysis classes for software problems and require further refinement.
systems. 8. Use cases are subject to change as stakeholders gain a
better understanding of requirements.
Example of CRC Modeling
- A simple CRC index card for the FloorPlan class lists Developing a UML Use Case Diagram for Home
responsibilities and collaborators: Security Function:
- FloorPlan 1. UML use case diagrams provide a graphical
Responsibilities: determineType(), positionFloorplan(), representation of interactions between actors and the system.
scale(), change color() 2. Actors are represented by stick figures, which can include
Attributes: type, name, outsideDimensions both human and non-human entities.
Collaborators: Wall, Camera 3. Use cases are represented by ovals within a box that
denotes the system boundary.
Connecting Class-Based and Data Modeling 4. The UML diagram includes primary and secondary
- Class-based modeling uses information from data actors, along with their channels of interaction.
modeling and scenarios to identify analysis classes. 5. Use cases are connected to actors with lines to show
- A grammatical parse can extract classes, attributes, and relationships and interactions.
operations from textual narratives for modeling purposes. 6. Use cases should be developed based on various
- Various UML modeling notations can be applied to homeowner interactions in a similar manner.
define hierarchies, relationships, associations, aggregations, 7. The UML diagram supplements the textual use case by
and dependencies among classes. providing a visual overview of system functionality.
8. It is essential to develop detailed use-case narratives to
Benefits of CRC Modeling accompany the UML diagram for clarity and completeness.
- CRC modeling aims to identify essential classes and their
interactions early in the design process.
- It provides a visual representation of class responsibilities
and collaborations, aiding in system understanding and
design decisions.
Page 01 of 02 Page 01 of 02
07082024 07082024
 21CS61 21CS61
Module-3 incremental development.
DOWNLOAD - XP encourages adaptability and the ability to embrace
changes during projects.
Q. 05 a Elucidate the concepts of extreme programming (XP) with L2 CO3 10
its functional Criticisms and Adaptations
Diagram - Critics argue that XP's incremental nature may limit
complex system design.
Elucidating the Concepts of Extreme Programming (XP) - Successful XP implementation requires recognizing
weaknesses and adapting the process to meet specific
organizational needs.

Conclusion
Extreme Programming (XP) stands out as one of the most
widely used agile processes, emphasizing rapid software
delivery, stakeholder involvement, and iterative
development cycles with a focus on simplicity and
adaptability.

b Elucidate SCRUM process with a neat diagram L2 CO3 10

Elucidating the SCRUM Process with a Neat Diagram

Overview of Extreme Programming (XP)
Extreme Programming (XP) is an agile process focused on
rapid software delivery to satisfy customer needs. It
involves four framework activities: planning, design,
coding, and testing, with an emphasis on creating frequent
software releases based on stakeholder priorities.

Core Values of XP
- XP is built on five core values: communication,
simplicity, feedback, courage, and respect.
- Effective communication between software engineers and
stakeholders is facilitated through close collaboration and
continuous feedback, minimizing extensive documentation.

XP Process and Activities

- XP follows an object-oriented approach and consists of Scrum
planning, design, coding, and testing activities. - Definition : Scrum is an agile software development
- The planning game initiates the process with requirements method emphasizing project priorities,
gathering to understand the business context. compartmentalized work units, communication, and
- XP emphasizes iterative development cycles to deliver frequent customer feedback.
software increments efficiently. - Origin : Conceived by Jeff Sutherland and his team in
the early 1990s.
XP Techniques and Practices - Activities : Guides development through
- XP suggests innovative techniques like pair programming requirements, analysis, design, evolution, and
and stakeholder involvement. delivery within a structured framework.
- It downplays extensive design in favor of simplicity and - Principles : Consistent with the agile manifesto,
Page 01 of 02 Page 01 of 02
07082024 07082024
 21CS61 21CS61
promoting agility and adaptability in the development time by the Scrum team to address evolving requirements
process. and challenges.
- Process Patterns : Utilizes software process patterns
for effective project management, including Backlog and SCRUM Process Diagram
Sprints. - Visual Representation : The diagram illustrates the
- Collaboration : Emphasizes collaboration within flow of the Scrum process, emphasizing project priorities
self-organizing teams for increased project success. , work units, communication, and customer feedback.
- Process Patterns : Highlighted in the diagram are the
Scrum Meetings key elements that define the Scrum methodology and
- Purpose : Held daily , these short meetings allow team guide development activities.
members to share progress, address obstacles, and plan for
the next tasks. OR
- Key Questions : Team members answer three Q. 06 a What is Agility? Explain Agility with the cost of change L2 CO3 10
questions: with Diagram.
1. What did you do since the last team meeting? Explain the Principles of Agile Software Development
2. What obstacles are you encountering?
3. What do you plan to accomplish by the next team Agility and Cost of Change Diagram
meeting?
- Leadership : Led by a Scrum master, the meeting
helps uncover potential problems early and promotes
knowledge socialization.

Demo Process
- Objective : Deliver the software increment to the
customer for evaluation, focusing on demonstrated
functionality within established time-box constraints.
- Functionality : Demos may not include all planned
features but showcase deliverable functions within set
time constraints.
- Importance : Allows for customer evaluation of
implemented features and ensures alignment with Agility in software development refers to a dynamic and
customer expectations. growth-oriented approach that embraces change. It
emphasizes rapid delivery of operational software, customer
Scrum Artifacts collaboration, flexibility in planning, and incremental
- Backlog : A prioritized list of project requirements or delivery strategies. One key aspect of agility is its impact on
features that provide business value for the customer. the cost of change. Traditional software development
- Sprints : Work units that aim to achieve specific experiences nonlinear cost increases as a project progresses,
requirements defined in the backlog within a making late changes expensive and time-consuming. In
predefined time-box. contrast, agility aims to flatten the cost of change curve,
- Product Manager 's Role : Assess the backlog, update allowing teams to accommodate changes late in a project
priorities as required, and ensure alignment with customer with minimal cost and time impact. Incremental delivery,
needs. continuous unit testing, and pair programming are agile
practices that help reduce the cost of change.
Process Patterns and Adaptability
- Dynamic Nature : Scrum process patterns enable
Principles of Agile Software Development
teams to work successfully in environments where
uncertainty and changes are inevitable. 1. Customer Satisfaction: Prioritize early and continuous
- Adaptation : Work within sprints is adapted in real-
Page 01 of 02 Page 01 of 02
07082024 07082024
 21CS61 21CS61
delivery of valuable software to satisfy the customer. during the software development process.
2. Embracing Change: Welcome changing requirements for
the customer's competitive advantage. Module-4
DOWNLOAD
3. Frequent Software Delivery: Deliver working software
frequently, with a preference for shorter timescales. Q. 07 a With example explain different categories of Software L2 CO4 10
4. Collaboration: Business people and developers must work Projects.
together daily throughout the project.
5. Motivated Individuals: Build projects around motivated
Different Categories of Software Projects
individuals and trust them to get the job done.
6. Effective Communication: Face-to-face conversation is
Objective-Driven vs. Product-Driven Projects
the most efficient way to convey information within the - Objective-driven projects focus on meeting specific
team. objectives that can be achieved in various ways, while
7. Progress Measurement: Working software is the primary product-driven projects aim to create a specified product as
measure of progress. requested by the client.
8. Sustainable Development: Agile processes promote - An example of an objective-driven project is one where an
sustainable development, maintaining a constant pace organization seeks recommendations to solve a problem,
indefinitely. leading to the need for a new software system.
Subsequently, a project is initiated to develop the software
These principles guide agile software development product based on these recommendations.
practices, focusing on customer satisfaction, adaptability to
change, collaboration, motivation, effective communication,
Examples of Software Projects
progress tracking, and sustainable development. 1. Getting married
2. Amending a financial computer system for the Euro
b Describe briefly the design modeling principles that guide L2 CO3 10 3. Researching human-computer interface quality
the respective framework activity 4. Investigating user issues with computer systems
5. Second-year programming assignment
Design Modeling Principles for Software Engineering 6. Operating system development for a new computer
7. Word processing software installation in an organization
Principles for Requirements Modeling:
1. Design should be traceable to the requirements model.
Characteristics of Software Development Projects
2. Always consider the architecture of the system to be - Software projects have particular difficulties due to the
built. relative invisibility of their products.
3. Design of data is as important as design of processing - Clear objectives are crucial for project success, but
functions. different stakeholders may have conflicting objectives,
necessitating a recognized overall project authority.
Principles for Design Modeling: - Effective communication channels and objective measures
1. Design should be traceable to the requirements model. of success are essential in projects involving multiple
2. Adapt the models you develop to the system at hand. individuals.
3. Try to build useful models, but forget about building
perfect models. Managing Software Projects
4. Don’t become dogmatic about the syntax of the model. - Modern software project management practices differ from
5. If your instincts tell you a model isn’t right, you traditional ones in various aspects, highlighting the evolving
probably have reason to be concerned. nature of managing software projects.
6. Get feedback as soon as you can. - Key aspects of modern software project management may
include agile methodologies, iterative development, and
These principles guide the respective framework activities enhanced collaboration tools.
in software engineering, ensuring the effectiveness and
adaptability of the design and requirements models created
Page 01 of 02 Page 01 of 02
07082024 07082024
 21CS61 21CS61
Outsourced Projects vs. Product Development objectives.
- Outsourced projects typically provide one-time revenue to 4. Focus on Desired Outcomes : Objectives should
a company, while product development projects can concentrate on desired project outcomes rather than task
generate revenue over several years. - based goals.
- Managing an outsourcing project differs from product 5 . Set Shared Intentions : Project objectives should
development in terms of project oversight, communication reflect shared intentions among stakeholders for
channels, and financial considerations. project success.
6. Prioritize Project Success Criteria : Define success
Software Product Development vs. Outsourced Projects - criteria based on the agreed functionality, required quality
Software product development involves creating a software , timeliness, and budget adherence.
product based on client specifications, while outsourced 7. Ensure Stakeholder Communication : Develop a
projects entail contracting external groups for specific tasks communication plan at the project 's outset to
. coordinate stakeholder efforts effectively.
- Outsourced projects have distinct management challenges 8. Recognize Different Interests : Acknowledge that
compared to in-house product development, such as different stakeholders may have varying objectives and
coordination with external vendors and ensuring project motivations, requiring effective communication and
alignment with business goals. negotiation.

b Explain the procedure of setting objectives for successful L2 CO4 10 Additional Considerations:
completion of - Sub -Objectives and Goals : Break down objectives
software project. into sub-goals that are within the control of individuals
or groups, ensuring progress towards the main objective.
Setting Objectives for Successful Completion of - Project vs . Business Objectives : Distinguish between
Software Project project objectives (targets for the project team ) and
business objectives (value realization ), ensuring alignment
Key Components of Setting Objectives: for overall success.
- Specific : Objectives should be concrete and well- - Theory W : Adopt a 'win-win' approach in software
defined to ensure clarity on project success criteria. project management to create situations where all parties
- Measurable : Objectives should have measures of benefit from project success.
effectiveness to gauge project success , such as
reducing customer complaints. OR
- Achievable : Objectives must be attainable by the Q. 08 a Differentiate between project management life cycle and L2 CO4 10
individual or group responsible for achieving them. software development life cycle and its phases
- Relevant : Objectives should align with the true
purpose of the project to ensure relevance. Differentiation between Project Management Life Cycle
- Time-Constrained : Objectives should have defined and Software Development Life Cycle
timeframes for achievement to provide a clear deadline.
Project Management Life Cycle:
Procedure for Setting Objectives: 1. Characteristics of Projects:
1. Define Clear Objectives : Ensure that project objectives - Non-routine tasks involved.
are specific, measurable, achievable, relevant, and time- - Specific objectives to be met or a specified product to
constrained (SMART criteria). be created.
2. Identify Stakeholders : Recognize stakeholders who - Work is carried out for someone other than yourself.
own the project, control financing, and set project - Work involves several specialisms.
objectives. - Work is carried out in several phases.
3. Establish Project Authority : Explicitly identify
project authority, often through a steering committee 2. Project Planning:
responsible for setting, monitoring, and modifying - Involves activities such as estimation, cost, duration,
Page 01 of 02 Page 01 of 02
07082024 07082024
 21CS61 21CS61
effort estimation. 1. Key Ideas:
- Scheduling based on estimations of effort and duration. - Software projects involve meeting specific objectives to
satisfy real needs.
3. Project Success Criteria: - Projects are non-routine and uncertain, requiring careful
- Success determined by the value of benefits exceeding management.
costs.
- Increasing development costs reduce profitability. b What is the role of management in execution of software L2 CO4 10
project development? Explain the Difference between
4. Project Objectives vs. Business Objectives: Traditional and Modern Project Management.
- Project objectives focus on agreed functionality, quality,
timeliness, and budget adherence. Role of Management in Software Project Development
- Business success depends on the value of benefits
exceeding costs. Management plays a crucial role in the execution of
software project development by overseeing various aspects
Software Development Life Cycle: of the project to ensure its success. Here are key points
1. Importance of Version Control: regarding the role of management in software project
- Increasing importance of tracking versions and development based on the provided document:
revisions in software development.
- Customization development models lead to multiple - Management is responsible for planning, monitoring, and
product versions. controlling software projects to ensure they meet objectives
and satisfy stakeholders' needs.
2. Change Management: - The project manager is involved in activities such as
- Project managers play a crucial role in product scheduling, staffing, risk management, and developing
baselining and version control. miscellaneous plans like quality assurance and configuration
- Change management is essential for successful project management plans.
delivery. - Project monitoring and control activities are crucial to
ensure that software development proceeds as planned, with
3. Modern Project Management Practices: the flexibility to adjust plans based on evolving project data.
- Goals include code reuse maximization and project - Project planning is a significant responsibility of the
duration compression. project manager, involving activities such as estimation of
- Emphasis on accommodating client feedback and cost, duration, and effort, which are critical for subsequent
incremental product delivery. scheduling and staffing decisions.

Phases of Project Development: Traditional vs. Modern Project Management

1. Project Development Stages:
- Customizing existing products for specific projects. Traditional project management practices differ from
- Key role of project manager in overseeing project modern approaches in various aspects, particularly in
development. response to the evolving nature of software development
projects. Here are key differences between traditional and
2. Main Stages of Software Projects: modern project management highlighted in the document:
- Scope definition of software project management.
- Understanding problems and concerns of software - Traditional project management focused on detailed
project managers. planning before project execution, while modern practices
- Identifying stakeholders, their objectives, and ensuring emphasize adaptive planning and rapid application
their satisfaction. development.
- Emphasis on careful planning, monitoring, and control. - Modern project management practices prioritize flexibility,
customer feedback, incremental delivery of products with
Conclusion: evolving functionalities, and responsiveness to change
Page 01 of 02 Page 01 of 02
07082024 07082024
 21CS61 21CS61
requests.
- Quality management, change management, and planning Q. 09 a List the popular capability models to manage the quality of L1 CO5 10
incremental delivery are key components of modern project the Software
management practices to meet customer demands for faster and write about SEI CMM with appropriate diagram.
delivery times and reduced costs.
- Modern project management emphasizes stakeholder Popular Capability Models for Software Quality
management and quality tracking throughout project Management
development, reflecting a shift towards more flexible and
customer-oriented approaches. SEI CMM (Software Engineering Institute Capability
Maturity Model)
SEI CMM is a reference model for appraising a software
development organization into one of five process maturity
levels. It assists organizations in improving the quality of
the software they develop. SEI CMM can be used for
capability evaluation and process assessment, with the
latter focusing on internal process improvement. The model
consists of different levels designed to help organizations
enhance their quality system gradually.

Key Features of SEI CMM:

- Helps predict contractor performance through evaluation
of development practices.
- Supports process improvement initiatives.
- Ranks organizations based on the quality of their
development processes.
- Can be used for both capability evaluation and internal
process assessment.

CMMI (Capability Maturity Model Integration) CMMI

is the successor of the Capability Maturity Model (
CMM) and is designed to be applicable across various
domains. It provides a framework for assessing an
organization's process maturity levels and includes key
process areas at different levels.

Key Aspects of CMMI:

- Released in versions 1.1 and 1.2 in 2002 and 2006
respectively.
- Used in domains beyond software development, such as
human resource management.
- Offers a generalized approach applicable to multiple
disciplines.
- Describes five distinct levels of process maturity.

Module-5 Other Popular Capability Models:

DOWNLOAD - ISO 15504
- Six Sigma

Page 01 of 02 Page 02 of 02
07082024 07082024
 21CS61 21CS61
These models, along with SEI CMM and CMMI, are utilization, efficiency compliance.
widely recognized for their effectiveness in managing - Maintainability: Includes analysability,
software quality through process-based techniques. changeability, stability, testability,
maintainability compliance.
Diagram for SEI CMM
Currently, a detailed diagram for SEI CMM is not provided
in the available content. However, the model visually OR
represents the five process maturity levels and how Q. 10 a Identify how Automation testing is preferred over manual L1 CO5 10
organizations progress through these levels to enhance their testing, with different tools used for Automation Testing
software development processes.
Automation Testing Advantages Over Manual Testing
b Explain the quality models: L2 CO5 10 and Tools Used
1) Garvin’s Quality Dimensions
2) Mccall Model Automation Testing Advantages Over Manual Testing
3) Boehms Model 1. Efficiency : Automated testing tools can rerun test
scripts easily and cheaply, reducing manual effort
Quality Models Overview significantly.
2. Cost-Effectiveness : Automation testing can
Garvin’s Quality Dimensions substantially reduce testing costs compared to manual
- Performance: The primary operating characteristics of testing.
a product or service. 3. Thoroughness : Automation testing allows for more
- Features: The additional characteristics that enhance a sophisticated test case design strategies, improving the
product's appeal. thoroughness of testing.
- Reliability: The probability of a product failing 4. Reliability : Automated test results are more reliable
within a specified time period. and eliminate human errors during testing.
- Conformance: The precision with which a product 5. Regression Testing : Automation simplifies repeated
meets its design specifications. running of test cases, especially after changes or error
- Durability: The life expectancy of a product. corrections.
- Serviceability: The ease of repair of a product. 6. Time-Saving : Automation testing can run a large
- Aesthetics: The subjective sensory characteristics of a number of test cases within a short period without
product. significant cost overhead.
- Perceived Quality: The quality as perceived by the 7. Maintenance : Helps in maintaining the test suite
customer. integrity as software undergoes changes over time.

McCall Model Tools Used for Automation Testing

- Product Revision: The ability to modify the 1. Test Script-Based Tools : Utilize scripts to drive
software. automated test tools, allowing for easy rerun of tests
- Product Transition: The ability to move the once debugged and verified.
software to a new environment. 2. Random Input Testing Tools : Generate test values
- Product Operation: The ability to operate the randomly to cover the input space of the unit under test,
software. cost-effective for finding certain types of defects.
- Product Revision: The ability to modify the 3. Capture and Playback Tools : Record test data
software. during manual execution and automatically replay tests,
- Product Transition: The ability to move the useful for regression testing but may require effort for
software to a new environment. maintenance.
4. Testing Tools Classification : Tools can be classified
Boehm's Model based on specific methodologies, with various options
- Efficiency: Involves time behavior, resource available from both public domain and commercial
Page 02 of 02 Page 02 of 02
07082024 07082024
 21CS61 21CS61
sources. 4. Production planning and review of customer
requirements.
b Explain Quality Management Systems with Principles of L2 CO5 10 5. Effective communication between customers and
BS EN ISO 9001:2000 suppliers.
6. Controlled design and development processes.
Quality Management Systems and Principles of BS EN 7. Proper control of design changes.
ISO 9001:2000 8. Measures for specifying and evaluating purchased
components.
Principles of BS EN ISO 9001:2000
1. Understanding customer requirements to meet or Benefits and Concerns
exceed them. - Controversy over standards' value and certification costs.
2. Leadership providing unity of purpose and direction for - Concern about certification distracting from actual
quality objectives. product quality problems.
3. Involvement of staff at all levels. - Standards applicable to all production, not just software
4. Focus on individual processes creating deliverable development.
products and services.
5. Emphasis on interrelated processes that deliver products Precautionary Steps for Work Contracted to ISO 9001
and services. Accredited Organizations
- Ensure alignment of quality standards and expectations.
Quality Management System (QMS) Components - Monitor and evaluate quality performance.
1. ISO 9000 describes fundamental features of a QMS and - Address any discrepancies promptly.
its terminology. - Maintain open communication for quality assurance.
2. ISO 9001 explains how a QMS applies to product Bloom’s Taxonomy Level: Indicate as L1, L2, L3, L4, etc. It is also desirable to indicate the
creation and service provision. COs and POs to be attained by every bit of questions.
3. ISO 9004 focuses on process improvement.
4. Continuous improvement of processes is a key aspect.
5. Decision-making based on factual evidence.
6. Building beneficial relationships with suppliers.

Implementation of QMS Principles

1. Determining customer needs and expectations.
2. Establishing a quality policy and defining quality
objectives.
3. Designing processes to meet quality objectives.
4. Allocating responsibilities for meeting requirements.
5. Ensuring resources for proper process execution.
6. Measuring process effectiveness and efficiency.
7. Gathering and analyzing measurements for
improvement.
8. Identifying and eliminating causes of discrepancies.
9. Continual improvement for an effective QMS.

ISO 9001 Requirements

1. Documentation of objectives, procedures, plans, and
records.
2. Management responsibility for actively managing QMS
and processes.
3. Allocation of adequate resources and trained staff.
Page 02 of 02 Page 02 of 02
07082024 07082024