Assignment Code: MCS-213/Assign/2024

Course Code: MCS-213

Assignment Name: Software Engineering

Year: 2024

Verification Status: Verified by Professor

Q1) Assume that you are assigned responsibility of developing an Online Admit Card Generation System (OACGS) for a university. OACGS should run both on PCs and Mobile Devices. OACGS will have all fields such as Student's name, Student's Address, Examination Centre Code and Address, Examination Centre Superintendent Name, Examination Centre e-mail address and Mobile Number, Aadhaar Number, Course Codes and Titles in whom the student is permitted for appearing in exams along with dates and timings of respective exams, Colour image of the student etc. The student will apply for examinations online by filling examination form. The validity of the data entered by the student shall be authenticated online and OACGS consisting of the above-mentioned information needs to be generated. Make assumptions wherever necessary.

For developing OACGS as specified above,

Q1. (a) Which SDLC paradigm will be selected. You may also suggest a SDLC paradigm that is proposed by you and non-existent as on date. Justify your answer.

Ans) The Software Development Life Cycle (SDLC) paradigm to be selected for developing the Online Admit Card Generation System (OACGS) for the University should be the Agile methodology.

Justification:

The Agile methodology is suitable for projects with evolving requirements, fast-paced development, and a focus on delivering working software iteratively. This approach allows for continuous feedback and collaboration with stakeholders, leading to a better understanding of the requirements and reducing the risks of project failure.

In the case of OACGS, the requirements may evolve over time, and it is important to deliver a working system as soon as possible. The Agile methodology is also suitable for developing applications that run on multiple platforms, as it allows for frequent testing and validation of the system on different devices.

Q1. (b) List the functional and non-functional requirements.

Ans) The functional and non-functional requirements are as follows:

Functional Requirements:

a) User Registration: Users (students) should be able to register on the OACGS platform by providing necessary information such as name, address, Aadhaar number, etc.

b) User Authentication: The system should authenticate users during the registration and login process to ensure the security of the system.

c) Examination Form: The system should provide an online form for students to fill out their examination details, including course codes, examination centre preferences, and exam dates and timings.

d) Data Validation: The system should validate the data entered by students to ensure accuracy and completeness. This includes validating Aadhaar numbers, email addresses, and mobile numbers.

e) Admit Card Generation: Once the examination form is submitted, the system should generate an admit card containing all the necessary information, including the student's name, examination centre details, course codes, exam dates, and a colour image of the student.

Non-Functional Requirements:

a) Security: The system should ensure the security and confidentiality of student data, including Aadhaar numbers and personal information.

b) Performance: The system should be able to handle multiple concurrent users without experiencing performance issues, ensuring smooth operation during peak times.

c) Usability: The user interface should be intuitive and user-friendly, allowing students to easily navigate the system and fill out examination forms without any confusion.

d) Reliability: The system should be reliable and available 24/7, with minimal downtime for maintenance or upgrades.

e) Scalability: The system should be scalable to accommodate future growth in the number of users and examination centres without requiring significant changes or upgrades.

f) Compatibility: The system should be compatible with different web browsers and operating systems, ensuring accessibility for all users regardless of their device or platform.

g) Compliance: The system should comply with relevant data protection laws and regulations, including GDPR, to ensure the privacy and security of student data.

h) Accessibility: The system should be accessible to users with disabilities, complying with accessibility standards such as WCAG to ensure inclusivity for all users.

Q1. (c) Estimate cost.

Ans) Estimating the cost of developing the Online Admit Card Generation System (OACGS) for a university involves considering various factors such as development time, resources, infrastructure, technology stack, and ongoing maintenance.

a) Development Time: The development time will depend on the complexity of the system, the number of features, and the size of the development team. Assuming a team of developers working full-time, the development time could range from several months to a year or more.

b) Human Resources: The cost of human resources includes salaries, benefits, and any additional expenses associated with hiring developers, designers, testers, and project managers.

c) Infrastructure: This includes the cost of hardware, software, servers, databases, and other infrastructure required to support the OACGS. This cost may vary depending on whether the system is hosted on-premises or in the cloud.

d) Technology Stack: The cost of software licenses, development tools, frameworks, and libraries used in building the OACGS. Open-source technologies may reduce costs, but there may still be expenses associated with customization and support.

e) Testing and Quality Assurance: The cost of testing and quality assurance activities to ensure that the OACGS meets the required standards of functionality, performance, security, and usability.

f) Data Security: Implementing robust data security measures to protect sensitive information such as Aadhaar numbers and personal data may require additional investment in encryption, access controls, and compliance with data protection regulations.

g) Maintenance and Support: Ongoing maintenance and support costs, including bug fixes, updates, and enhancements to the OACGS after it has been deployed. This may involve retaining a dedicated support team or outsourcing maintenance to a third-party provider.

h) Training: Training costs for end-users, administrators, and support staff to ensure they are proficient in using and managing the OACGS effectively.

i) Contingency: It's essential to budget for unexpected expenses or changes in requirements that may arise during the development and deployment of the OACGS.

Q1. (d) Estimate effort.

Ans) Estimating the effort required to develop the Online Admit Card Generation System (OACGS) involves considering various factors such as the complexity of the system, the number of features, the size and expertise of the development team, and the development methodology being used.

a) Requirements Gathering and Analysis: This phase involves gathering and analysing requirements from stakeholders, including university administrators, exam coordinators, and students. Effort is required to understand the specific needs and objectives of the OACGS.

b) Design: The design phase involves creating the architectural design, database design, user interface design, and other technical specifications for the OACGS. Effort is required to translate the requirements into a detailed design that can guide the development process.

c) Development: This phase involves coding the software components of the OACGS, including frontend development for both PC and mobile devices, backend development, database development, and integration of third-party services for Aadhaar authentication, email communication, etc. Effort is required to implement the functionalities according to the design specifications.

d) Testing: The testing phase involves various types of testing, including unit testing, integration testing, system testing, and user acceptance testing (UAT). Effort is required to identify and fix defects, ensure that the OACGS meets quality standards, and validate that it fulfils the requirements.

e) Training and Documentation: Effort is required to develop training materials for end-users, administrators, and support staff, as well as to conduct training sessions to ensure that they are proficient in using and managing the OACGS. Documentation needs to be created to provide instructions, guidelines, and troubleshooting information.

f) Maintenance and Support: Effort is required for ongoing maintenance and support activities, including bug fixes, updates, enhancements, and providing technical support to users. Effort is also needed to monitor the performance and security of the OACGS and to address any issues that may arise post-deployment.

Q1. (e) Develop SRS using IEEE format.

Ans) Software Requirements Specification (SRS) for Online Admit Card Generation System (OACGS)

Introduction

Purpose: The purpose of the Online Admit Card Generation System (OACGS) is to provide a platform for students to apply for examinations online and generate their admit cards. The system will run on both PCs and mobile devices and will include features such as student registration, examination form submission, data validation, and admit card generation.

Scope: The scope of OACGS includes capturing student information, examination centre details, course codes and titles, exam dates and timings, and generating admit cards with the necessary information. The system will authenticate the data entered by students online to ensure its validity.

Definitions, Acronyms, and Abbreviations:

a) OACGS: Online Admit Card Generation System

b) SRS: Software Requirements Specification

c) PC: Personal Computer

References:

a) University examination regulations and policies

b) IEEE Standard for Software Requirements Specifications (IEEE Std 830-1998)

Overview:

a) This document provides a detailed description of the requirements for the development of OACGS. It outlines the functional and non-functional requirements, user interfaces, and system constraints.

Overall Description

Product Perspective:

a) OACGS is a standalone system that interacts with users through a web-based interface.

b) It may integrate with other university systems for data validation and authentication.

Product Functions:

a) User Registration: Allow students to register on the system by providing personal information.

b) Examination Form Submission: Enable students to fill out examination forms online.

c) Data Validation: Validate the data entered by students to ensure accuracy and completeness.

d) Admit Card Generation: Generate admit cards with student information (name, address, Aadhaar number, colour image of the student), examination centre details (centre code, address), course codes, exam dates and timings.

User Characteristics

Users of OACGS include students applying for examinations, examination centre administrators, and system administrators. They may have varying levels of technical expertise.

Constraints

a) The system must comply with university regulations and data protection laws.

b) The system should be accessible on both PCs and mobile devices.

Assumptions and Dependencies

a) Assumption: Students have access to the internet and a device capable of accessing the OACGS platform.

b) Dependency: Integration with university databases for data validation and authentication.

Specific Requirements

External Interfaces

1) User Interface

a) The user interface should be intuitive and easy to navigate.

b) The interface should be responsive and compatible with different web browsers and screen sizes.

2) Hardware Interface

a) OACGS should be accessible on PCs, laptops, tablets, and smartphones.

3) Software Interface

b) OACGS should integrate with university databases for data validation and authentication.

Functional Requirements

1) User Registration: Students should be able to register on the system by providing their name, address, Aadhaar number, etc.

2) Examination Form Submission: Students should be able to fill out examination forms online, including course codes, examination centre preferences, and exam dates and timings.

3) Data Validation: The system should validate the data entered by students, including Aadhaar numbers, email addresses, and mobile numbers.

4) Admit Card Generation: Upon submission of the examination form, the system should generate an admit card containing student information, examination centre details, course codes, exam dates, and a colour image of the student.

Non-Functional Requirements

a) Security: The system should ensure the security and confidentiality of student data.

b) Performance: The system should be able to handle multiple concurrent users without experiencing performance issues.

c) Usability: The user interface should be intuitive and user-friendly.

d) Reliability: The system should be reliable and available 24/7.

e) Scalability: The system should be scalable to accommodate future growth in the number of users and examination centres.

f) Compatibility: The system should be compatible with different web browsers and operating systems.

g) Accessibility: The system should be accessible to users with disabilities.

h) Compliance: The system should comply with relevant data protection laws and regulations.

Q1. (f) List queries for whom Reports can be generated

Ans) Reports can be generated for various queries such as:

1) Student enrolment-wise admit card details.

2) Student Admit Card Status details.

3) Examination centre’s code-wise admit card details.

4) Course code or title-wise admit card details.

5) Examination centre contact details.

Q1. (g) List specific requirements which enables OACGS to run on both PCs and Mobile Devices.

Ans) To ensure that the Online Admit Card Generation System (OACGS) runs smoothly on both PCs and mobile devices, specific requirements need to be considered. Here are the specific requirements:

1) Responsive design that adapts to different screen sizes

2) Cross-browser compatibility

3) Support for multiple operating systems.

4) Mobile-friendly interface with touch gestures and mobile-specific features

5) Integration with mobile app stores (if applicable)