Sub Name/Code: Software Engineering & Project Management [21CS61]

Sem: VI
Assignment – I

Sl. Bloom’s
Questions (Answer all the Questions) CO Marks
No. Level

Explain the different UML notations and provide examples of how each CO2 L2 10
1.
notation is used to represent elements in a class diagram.
As software becomes more pervasive, risks to the public (due to faulty
programs) become an increasingly significant concern. Develop a CO1 L3 10
2.
doomsday but realistic scenario in which the failure of a computer
program could do great harm (either economic or human).
3. Problem Scenario: CO2 L3 10
As the head of information systems for a college you are tasked with
developing a new student registration system. The college would like a
new client-server system to replace its much older system developed
around mainframe technology. The new system will allow students to
register for courses and view report cards from personal computers
attached to the campus LAN. Professors will be able to access the system
to sign up to teach courses as well as record grades.
Due to a decrease in federal funding, the college cannot afford to replace
the entire system at once. The college will keep the existing course
catalog database where all course information is maintained. This
database is an Ingres relational database running on a DEC VAX.
Fortunately, the college has invested in an open SQL interface that allows
access to this database from college’s Unix servers. The legacy system
performance is rather poor, so the new system must ensure that access to
the data on the legacy system occurs in a timely manner. The new system
will access course information from the legacy database but will not
update it. The registrar’s office will continue to maintain course
information through another system.
At the beginning of each semester, students may request a course
catalogue containing a list of course offerings for the semester.
Information about each course, such as professor, department, and
prerequisites, will be included to help students make informed decisions.
The new system will allow students to select four course offerings for the
coming semester. In addition, each student will indicate two alternative
choices in case the student cannot be assigned to a primary selection.
Course offerings will have a maximum of ten students and a minimum of
three students. A course offering with fewer than three students will be
 cancelled. For each semester, there is a period of time that students can
change their schedule. Students must be able to access the system during
this time to add or drop courses. Once the registration process is
completed for a student, the registration system sends information to the
billing system so the student can be billed for the semester. If a course
fills up during the actual registration process, the student must be notified
of the change before submitting the schedule for processing.
At the end of the semester, the student will be able to access the system to
view an electronic report card. Since student grades are sensitive
information, the system must employ extra security measures to prevent
unauthorized access.
Professors must be able to access the on-line system to indicate which
courses they will be teaching. They will also need to see which students
signed up for their course offerings. In addition, the professors will be
able to record the grades for the students in each class.
Provide Use Case Specification for the above scenario:

Use Case ID: {This should be coded to identify the owning team and the
level of the use case}
Use Case Name: {Short descriptive phrase}
Relevant requirements: {Reference to other relevant requirements
documents.}
Primary Actor: {Main sub-system/entity that initiates use}
Pre-conditions: {Requirements on the state of the system prior to this use
being valid.}
Post-conditions: {This describes the state of the system following the
successful completion of this use. effects on other systems and actors may
also be described.}
Basic Flow or Main Scenario: {Numbered flow of events: 1 The user
initiates an action by… 2 The system responds by...}
Extensions or Alternate Flows: {This section presents variations on this
use case. It presents those use cases that have an extends relation with the
current use case.}
Exceptions: {This section describes all error conditions that can arise in
the use case.}
Related Use Cases: {use cases that are either usually performed just
before or after the current use.}

4. Analyze the given case study and choose either the Waterfall or CO3 L4 10
Evolutionary process model. Justify your choice by comparing
the strengths and weaknesses of both models in the context of
the case study.

I. Case Study Ideas on Waterfall Model: [Choose any one]

 a. Development of a Banking System
b. Enterprise Resource Planning (ERP) System
Implementation
c. Military Defense System Development
d. Healthcare Management System

II. Case Study Ideas on Evolutionary Process Models: [Choose

any one]
a. Development of a Mobile Application
b. E-Commerce Website Development
c. Smart Home Automation System
d. Customer Relationship Management (CRM) System

Class diagrams are a powerful way to visualize the structure of a

system by showing its classes, their attributes, operations, and the
relationships among objects. Analyze the given topics [Choose any
one] using class diagrams:
a. E-Commerce Platform
b. Library Management System
c. Hospital Management System
5. d. University Information System CO2 L4 10
e. Banking System
f. Online Booking System
g. Inventory Management System
h. Customer Relationship Management (CRM) System
i. Social Media Platform
j. Content Management System
Note: Enclose the colour printoutwith the assignment book

Course Instructor HOD

Q4. I. Case Study Ideas on Waterfall Model in Software Engineering

a. Development of a Banking System:

 Context: Develop a comprehensive banking software system, including modules for
account management, transactions, loans, and customer service.
 Focus: Highlight the step-by-step phases from requirement gathering, design,
implementation, testing, and maintenance.
 Challenges and Solutions: Discuss how the rigidity of the Waterfall model impacts the
project, especially in the face of requirement changes.

b. Enterprise Resource Planning (ERP) System Implementation:

 Context: Implement an ERP system for a manufacturing company to integrate various
business processes such as inventory, HR, finance, and production.
 Focus: Emphasize the documentation process and the importance of detailed planning
in the Waterfall model.
 Outcome: Analyze the effectiveness of the Waterfall model in meeting predefined
requirements within a specified timeline.

c. Military Defense System Development:

 Context: Develop a defense system for a government entity with strict compliance and
security requirements.
 Focus: Showcase the application of the Waterfall model in highly regulated
environments where thorough documentation and validation at each stage are crucial.
 Evaluation: Assess the pros and cons of using Waterfall in a project where changes
are minimal and well-defined.

d. Healthcare Management System:

 Context: Design and develop a healthcare management system for a hospital,
including patient records, appointment scheduling, billing, and medical history
tracking.
 Focus: Illustrate how the Waterfall model manages complex interdependencies and
ensures compliance with healthcare regulations.
 Reflection: Discuss how the sequential approach helps in managing large-scale
projects but may pose difficulties with late-stage requirement changes.

II. Case Study Ideas on Evolutionary Model in Software Engineering

a. Development of a Mobile Application:

 Context: Create a mobile application for a social media platform with evolving user
requirements and frequent updates.
 Focus: Highlight the iterative cycles of development, user feedback integration, and
continuous improvement.
 Challenges and Solutions: Discuss managing user expectations and balancing between
evolving features and maintaining stability.

b. E-Commerce Website Development:

 Context: Build an e-commerce platform for a retail business with dynamic features
such as product listings, customer reviews, and payment gateways.
  Focus: Emphasize how the Evolutionary model supports frequent changes and rapid
feature additions based on user feedback and market trends.
 Outcome: Analyze the benefits of continuous delivery and deployment in adapting to
competitive pressures.

c. Smart Home Automation System:

 Context: Develop a smart home automation system with components like lighting
control, security, and energy management, where requirements evolve based on
technological advancements.
 Focus: Showcase the iterative prototyping and user testing cycles to refine features.
 Evaluation: Assess the impact of using the Evolutionary model on user satisfaction
and product innovation.

d. Customer Relationship Management (CRM) System:

 Context: Implement a CRM system for a growing business, requiring regular updates
and new features to enhance customer interaction and data analysis.
 Focus: Demonstrate the flexibility of the Evolutionary model in accommodating
changing business needs and integrating customer feedback.
 Reflection: Discuss the trade-offs between rapid iterations and maintaining code
quality and system performance.

Q5. Class Diagrams:

a. E-Commerce Platform: Analyze the structure of an online shopping system [Classes:

User, ShoppingCart, Product, Order, Payment, Shipping, Review]
b. Library Management System: Understand the organization and operations of a library
system. [Classes: Book, Member, Loan, Librarian, Catalogue, Reservation]
c. Hospital Management System: Model the key components and interactions within a
hospital setting. [Classes: Patient, Doctor, Nurse, Appointment, MedicalRecord,
Prescription, Department]
d. University Information System: Analyze the academic and administrative processes
of a university. [Classes: Student, Professor, Course, Enrollment, Department,
Schedule, Grade]
e. Banking System: Model the operations and relationships in a banking environment.
[Classes: Account, Customer, Transaction, Loan, Branch, Employee]
f. Online Booking System: Understand the process of booking services online, such as
for hotels or flights. [Classes: Booking, User, Service, Payment, Review, Invoice]
g. Inventory Management System: Model the tracking and management of inventory in
a warehouse or store. [InventoryItem, Supplier, Order, Warehouse, Stock, Category]
h. Customer Relationship Management (CRM) System: Analyze the components and
workflows within a CRM system. [Classes: Customer, Contact, SalesOpportunity,
Lead, Campaign, Interaction]
i. Social Media Platform: Model the entities and their interactions within a social media
environment. [Classes: User, Post, Comment, Like, Message, Group, Event]
j. Content Management System: Analyze the structure and workflows of a CMS.
[Classes: Content, User, Role, Permission, Media, Category, Tag]
Course Instructor HOD