OBJECT ORIENTED SOFTWARE ENGINEERING

1.Write a Software Requirement Specification as per SRS IEEE temptate for the
scenario.

Ans: 1.1 Purpose

The purpose of this document is to specify the requirements for the development of the Student
Management System (SMS). This document serves as a reference for all stakeholders involved in the
project, including developers, testers, administrators, and users.

1.2 Scope

The SMS is designed to manage student-related information within an educational institution. It

encompasses functions related to student enrollment, course registration, grading, attendance tracking,
and reporting.

1.3 Definitions, Acronyms, and Abbreviations

 SMS: Student Management System

 GUI: Graphical User Interface
 DBMS: Database Management System

2. Overall Description

2.1 Product Perspective

The SMS will operate as a standalone system with the ability to integrate with existing educational
systems via APIs for data exchange.

2.2 Product Functions

2.2.1 Student Registration

 Allow administrators to add, update, and delete student records.

 Generate unique student IDs.
 Capture student personal information.

2.2.2 Course Management

 Enable administrators to create, modify, and delete course details.

 Assign instructors to courses.
 Define course prerequisites.

2.2.3 Attendance Tracking

 Record student attendance for each class session.

 Generate attendance reports.

2.2.4 Grading

 Input and calculate student grades.

 Calculate GPA and CGPA.
 OBJECT ORIENTED SOFTWARE ENGINEERING

 Generate grade reports.

2.2.5 User Authentication and Authorization

 Authenticate users (admins, instructors, and students) securely.

 Manage user roles and permissions.

2.3 User Classes and Characteristics

The SMS will be used by the following user classes:

 Administrators: Responsible for system setup and student record management.

 Instructors: Manage courses, record attendance, and input grades.
 Students: Access their course information, grades, and attendance.

2.4 Operating Environment

The SMS will operate on the following platforms:

 Web browsers (Chrome, Firefox, Safari).

 Compatible with Windows, macOS, and Linux operating systems.

2.5 Design and Implementation Constraints

 The system must be implemented using [programming language/technology stack].

 Data will be stored in a [DBMS].
 Compliance with relevant data protection regulations (e.g., GDPR, FERPA).

2.6 Assumptions and Dependencies

 Availability of hardware and network infrastructure.

 Availability of third-party libraries and tools for development.

3. System Features

3.1 Student Registration

3.1.1 Description and Priority

 Description: This feature allows administrators to manage student records, including personal
information and enrollment details.
 Priority: High

3.1.2 Stimulus/Response Sequences

 Stimulus: Admin inputs student information.

 Response: System updates the student database.

3.2 Course Management

3.2.1 Description and Priority

 OBJECT ORIENTED SOFTWARE ENGINEERING

 Description: Instructors and administrators can create, modify, and manage course information.
 Priority: High

3.2.2 Stimulus/Response Sequences

 Stimulus: Instructors/admins input course details.

 Response: System updates the course database.

...

(Continue with detailed feature descriptions for attendance tracking, grading, authentication, etc.)

4. External Interface Requirements

4.1 User Interfaces

The SMS will provide a user-friendly web-based GUI for all user classes.

4.2 Hardware Interfaces

The system will interact with standard computer hardware components, including servers and
networking equipment.

4.3 Software Interfaces

The SMS will integrate with existing systems through RESTful APIs for data exchange.

5. Non-Functional Requirements

5.1 Performance Requirements

 The system should respond to user actions within 2 seconds.

 The system should support a minimum of 500 concurrent users.

5.2 Security Requirements

 User data should be encrypted during transmission.

 User authentication should follow best security practices.

5.3 Software Quality Attributes

 The system should be maintainable with clear code documentation.

 Regular backups of the database should be performed.

6. Other Requirements

 The system should have an online help and support section.

 The system should be accessible from mobile devices.

7. Appendix
 OBJECT ORIENTED SOFTWARE ENGINEERING

(Include any additional information or diagrams as needed.)

2.A system is to be developed for scheduling the courses in MCA programme,based on the input
about classrooms, lecture times, and time preferences of the different instructors.
Ans: Purpose
The Course Scheduling System is designed to streamline the scheduling of courses within the MCA
program. It takes into account classroom availability, lecture times, and instructor preferences to create
an efficient and conflict-free course schedule.
Features
1. Instructor Preferences
Instructors can input their preferred lecture times and constraints.
Preferences may include specific days, time slots, and any restrictions.
2. Classroom Allocation
The system allocates classrooms based on course requirements and classroom availability.
It optimizes classroom assignments to avoid conflicts.
3. Schedule Generation
The system generates a final course schedule that minimizes conflicts and meets instructor preferences.
Administrators have the option to manually adjust the schedule if necessary.
Users
Administrators: Responsible for system setup and schedule generation.
Instructors: Provide input regarding their course preferences.
Students: Access the final course schedule.
Technology
The system will be web-based, accessible via standard web browsers.
It may integrate with other university systems or databases for data exchange.
Constraints
The system should perform efficiently and support scheduling for a significant number of courses.
Security measures should be in place to protect scheduling data.
User data should be encrypted during transmission.
Regular backups of scheduling data should be performed.
 OBJECT ORIENTED SOFTWARE ENGINEERING

3.A web based application is to be developed for e-administration of computer labs of an

institution which eases the tasks of the administrator, instructors, HoDs of various departments,
technical staff and students The computing facilities includes computers, Printers, LCDS,
Digital Boards etc. on a 24×7basis to carry out academic experiments with all the necessary
software installed and configured. The software should also help the administrator and
instructors to maintain proper documentation of the computing systems.
Ans: Developing a web-based application for the e-administration of computer labs in an institution is
a complex project that requires careful planning and consideration of various functionalities. Here is
an outline of the key features and functionalities that should be included in such an application:
1. User Roles and Access Control:
1. Super Administrator: Has overall control and access to all features.
2. Department Heads (HoDs): Can manage labs and resources within their departments.
3. Instructors: Can schedule and manage lab sessions.
4. Technical Staff: Responsible for hardware and software maintenance.
5. Students: Can check lab availability and make reservations.
2. Lab and Resource Management:
Add, edit, and remove labs and resources (computers, printers, LCDs, digital boards).
Assign resources to specific labs and maintain an inventory.
3. Lab Reservation System:
1. Students and instructors should be able to book lab sessions in advance.
2. Set availability slots for each lab.
3. Automatic notifications of reservations to all concerned parties.
4. Software Management:
1. Keep a record of all software installed on lab computers.
2. Update and maintain software licenses.
3. Alert for software updates and license renewals.
5. Documentation and Reporting:
1. Maintain detailed documentation of each lab's configuration.
2. Generate reports on lab usage, resource allocation, and maintenance schedules.
6. Maintenance and Support:
1. Enable technical staff to schedule maintenance tasks.
2. Keep track of hardware issues and resolutions.
3. Automated alerts for hardware failures.
7. Notifications and Communication:
1. Send email or SMS notifications for reservation confirmations, cancellations, and reminders.
2. Allow users to submit support requests and inquiries.
8. User-Friendly Interface:
1. An intuitive and responsive web interface for all users.
2. Mobile-friendly design for on-the-go access.
9. Security:
 OBJECT ORIENTED SOFTWARE ENGINEERING

1. Implement user authentication and authorization mechanisms.

2. Regularly update and patch the application to protect against security vulnerabilities.
10. Scalability and Performance:
- Ensure the system can handle a large number of users and lab resources.
- Optimize database performance for efficient data retrieval.
11. Backup and Recovery:
- Regularly back up application data and configurations.
- Implement a disaster recovery plan.
12. Integration:
- Integrate with the institution's existing databases and systems, such as student records.
13. Training and Support:
- Provide training for administrators, instructors, and technical staff.
- Offer ongoing technical support for users.
14. Compliance:
- Ensure that the application complies with data protection regulations and institutional policies.
15. User Feedback and Improvement:
- Collect user feedback and make regular updates to improve the system based on user needs.
16. Documentation:
- Create user manuals and documentation for system administrators and users.
17. Testing:
- Rigorous testing for functionality, security, and performance.
18. Deployment and Maintenance:
- Plan for a smooth deployment process, including data migration if necessary.
- Establish a maintenance schedule for regular updates and improvements.

19. Budget and Resources:

- Allocate budget and resources for development, hardware, and ongoing maintenance.

20. User Training:

- Conduct training sessions for all user roles to ensure they can effectively use the system.
-This project will require collaboration between software developers, system administrators, and other
stakeholders to ensure the successful development and deployment of the e-administration system for
computer labs in the institution. It's important to continuously gather feedback from users and make
iterative improvements to meet evolving needs.
 OBJECT ORIENTED SOFTWARE ENGINEERING

4.Institute of Management studies (IMS) has organised an International conference with various
subject tracks. The conference details are uploaded on the web site developed by the institute. A
participant has to register online under category student, Faculty member, Research scholar and
corporate. He/She has to upload an abstract of his/her paper. If It gets selected he/she has to
upload final paper along with the registration fee. The registration fee varies according to the
category of the participants. The payment should be done online. The paper presentation schedule
will be displayed on the website under the defined tracks. After the conference, the presented
papers get published in online journal and particapants can give his/her feedback on line. Draw
the following diagrams for the above case:
a) Use Case Diagram [10]
Ans:

b) Class Diagram [10]

 OBJECT ORIENTED SOFTWARE ENGINEERING

Ans:

5.Draw Activity diagram for registering a billing complaint to MSEB.[10]

Ans:

6.Draw State Transition Diagram for a toy Robot, with following functionalities. [10]
i) When the Robot is SWITCHED ON, it should greet as per the time
(Morning, Afternoon etc)
 OBJECT ORIENTED SOFTWARE ENGINEERING

ii) It should behave as per your order - “Walk Straight” ‘Run”, and
“Stop”.
iii) Set time for the robot
iv) After 6pm, it SWITCHES ON it own lights.
v) When the battery is down it gives an indication for charging it by
saying “Battery Down?” Similarily, after the charging is complete it
says “Battery Full”.

7.Elaborate on the artefacts in Scrum. [4]

1. Ans: In software development, the term “artifact” refers to information that stakeholders and
the scrum team use to describe a product that’s being developed.
2. Scrum artifacts define the work that must be done, and they always add value during a sprint.
In simple terms, scrum artifacts can be seen as nuggets of vital information for the scrum
team. They provide structure to the scrum process because they act as guidelines for the
product development plan.
3. This is vitally important, especially for distributed teams who may work from home because
it provides a platform where they can see how they’re doing on a particular sprint. This keeps
everyone on the same page, no matter where they are.
4. ProjectManager is cloud-based work and project management software that connects hybrid
teams. No matter where or when your scrum team works, they can share scrum artifacts in
real time. Our kanban board makes it easy for scrum teams to manage their artifacts and then
collaborate to plan sprints. Product owners get visibility into the process to reallocate
resources to avoid bottlenecks

8.Enumerate the attributes of web-based systems and Applications. [4]

Ans: Web Applications attributes to create situations that monitor web application performance and
application server loads.

The Web Applications attributes provide aggregated information for each web application and for the
application server running that application. These performance data describe all servlets and JSPs
deployed to that web application as well as performance data for all servlets and JSPs running in the
application server. Examples include the number of loaded servlets and JSPs and total requests. The
attributes within this group are used to build the Web Applications workspace.

Average Concurrent Requests The average number of concurrent requests for servlets and JSPs
during the interval. The valid format is a decimal (formatted to three decimal places). This value is an
average of several values collected over an interval. The interval can be either between this time and
the previous time you activated this workspace, or fixed (normally 60 seconds), depending on the
configuration of the Monitoring Agent.

Average Response Time (ms) The average time (in milliseconds) required for a servlet to perform a
task during the interval. Calculated by dividing the total responses by Request Count; if Request
Count is zero, this value is set to blank. The valid format is a decimal (formatted to three decimal
places).
 OBJECT ORIENTED SOFTWARE ENGINEERING

Virtual Host Name The name of the virtual host. The valid format is an alphanumeric string, with a
maximum of 64 characters.

Enterprise Application Name The name of the Enterprise application. The valid format is an
alphanumeric string, with a maximum of 128 characters.

Error Count The number of errors or exceptions that have occurred in the servlet. The valid format is
a positive integer.

Error Rate (per sec) The servlet exceptions or errors (per second) for the interval since the previous
sample. The valid format is a decimal (formatted to three decimal places).

Instrumentation Level The web instrumentation level for this web application. For WebSphere 5, the
valid values are None, Low, Medium, High, and Maximum. For WebSphere 6 or higher, the valid
values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.

Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.

Node Name The name of the system on which the server is running. The valid format is an
alphanumeric string, with a maximum of 256 characters.

Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a
maximum of 128 characters.

Request Count The number of total requests for the servlet during the interval. The valid format is a
positive integer.

Request Rate (per sec) The servlet requests (per second) for the interval since the previous sample.
The valid format is a decimal (formatted to three decimal places).

Sample Date and Time The date and time the Tivoli Enterprise Monitoring Agent collected the data.
The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is
MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:

9.Explain the four values of Agile Manifesto with its meaning. [4]

Ans: 4 values of Agile

The four core values of Agile software development as stated in the Agile Manifesto are as follows:

1. Individuals and interactions over processes and tools.

2. Working software over comprehensive documentation.

3. Customer collaboration over contract negotiation.

4. Responding to change over following a project plan.

 OBJECT ORIENTED SOFTWARE ENGINEERING

10. Elaborate on any four Extreme Programming Practices. [4]

Ans: The following diagram shows how Extreme Programming is woven around the Extreme
Programming practices −

The Planning Game

The main planning process within extreme programming is called the Planning Game. The game is a
meeting that occurs once per iteration, typically once a week. The Planning Game is toqQuickly
determine the scope of the next release by combining business priorities and technical estimates. As
reality overtakes the plan, update the plan.

Business and development need to make the decisions in tandem. The business decisions and the
development’s technical decisions have to align with each other.

Business people need to decide about −

 Scope − How much of a problem must be solved for the system to be valuable in production?
The businessperson is in a position to understand how much is not enough and how much is
too much.
 Priority − If you are given an option, which one do you want? The businessperson is in a
position to determine this, more than a developer with inputs from the customer.
 Composition of releases − How much or how little needs to be done before the business is
better off with the software than without it? The developer's intuition about this question can
be wildly wrong.
 Dates of releases − What are important dates at which the presence of the software (or some
of the software) would make a big difference?

Technical people need to decide about −

 OBJECT ORIENTED SOFTWARE ENGINEERING

 Estimates − How long will a feature take to implement?

 Consequences − There are strategic business decisions that should be made only when
informed about the technical consequences. Development needs to explain the consequences.
 Process − How will the work and the team be organized? The team needs to fit the culture in
which it will operate. The software must be written well rather than preserve the irrationality
of an enclosing culture.
 Detailed Scheduling − Within a release, which stories should be done first? The developers
need the freedom to schedule the riskiest segments of development first, to reduce the overall
risk of the project. Within that constraint, they still tend to move business priorities earlier in
the development, reducing the chance that important stories will have to be dropped towards
the end of the development of a release due to time constraints.

Thus, plan is a result of collaboration between the customer, businessperson and the developers.

11.Draw the User Interface Screen to lodge a grievence against noise pollution in your
neighbourhood on the government noise pollution grievance redressal and monitoring system.
[4]
Ans:

12.Draw the user Interface Screen to generate vistors Gate pass. [4]
 OBJECT ORIENTED SOFTWARE ENGINEERING

Ans:

13.Draw the use case and class diagram for a placement agency site which providesthe facility
for the condidate to register with their academic details, personal details & skill sets.
Organizations can also register with their requirements. Searching faciltity is provided for
searching job as well as condidate. [20]
 OBJECT ORIENTED SOFTWARE ENGINEERING

Ans:

14.Draw state transition diagram for vending machine placed at super market. [10]
 OBJECT ORIENTED SOFTWARE ENGINEERING

Ans:

15.Draw Activity diagram for ordering grocery using mobile App. [10]
Ans:
 OBJECT ORIENTED SOFTWARE ENGINEERING

16.Attempt any two. [8]

a) Explain extreme Programing (XP)
Ans: Extreme programming (XP) is one of the most important software development frameworks of
Agile models. It is used to improve software quality and responsiveness to customer requirements.
The extreme programming model recommends taking the best practices that have worked well in the
past in program development projects to extreme levels.
Good practices need to be practiced in extreme programming: Some of the good practices that
have been recognized in the extreme programming model and suggested to maximize their use are
given below:
 Code Review: Code review detects and corrects errors efficiently. It suggests pair programming
as coding and reviewing of written code carried out by a pair of programmers who switch their
works between them every hour.
 Testing: Testing code helps to remove errors and improves its reliability. XP suggests test-driven
development (TDD) to continually write and execute test cases. In the TDD approach, test cases
are written even before any code is written.
 Incremental development: Incremental development is very good because customer feedback
is gained and based on this development team comes up with new increments every few days
after each iteration.
 Simplicity: Simplicity makes it easier to develop good quality code as well as to test and debug
it.
 Design: Good quality design is important to develop good quality software. So, everybody should
design daily.
 Integration testing: It helps to identify bugs at the interfaces of different functionalities. Extreme
programming suggests that the developers should achieve continuous integration by building and
performing integration testing several times a day.

b) What are 12 manifesto of Agile development?

Ans:
 OBJECT ORIENTED SOFTWARE ENGINEERING

c) Write a difference between Agile and scrum.

Ans:

Aspect Agile Scrum

Agile is a collaborative and

flexible approach used to Scrum is an Agile framework that
Definition efficiently accomplish tasks, promotes collaboration and efficiency in
particularly in software software development through sprints.
development.

Agile teams work on various Scrum divides projects into small builds
Iterative iterations of a project, organized called sprints, with each sprint having
Approach into a prioritized backlog based product backlogs, sprint backlogs, and
on end-user feedback. sprint goals.

Agile emphasizes flexibility and Scrum is more structured and less

Project
adaptability, allowing changes as flexible, making it ideal for those aiming
Flexibility
needed throughout the project. to deliver results quickly.
 OBJECT ORIENTED SOFTWARE ENGINEERING

Agile delivers software regularly

Software
for feedback, enabling Scrum delivers software after each sprint
Delivery
continuous iteration of of development.
Frequency
development and testing.

Agile is suitable for smaller

Suitable Team teams and those who prefer Scrum is more suited for creative and
Size simplicity in design and experimental approaches.
execution.

d) Write a short note on Feature Drive Development (FDD).

ANs: Feature Driven Development (FDD) is an agile framework that, as its name suggests, organizes
software development around making progress on features. Features in the FDD context, though, are
not necessarily product features in the commonly understood sense.