E-Commerce website

Session:

BS IT 2023-2025

Supervisor: Sir Husnain

Submitted By:

Sr# Student name Reg No.

01 Muzammal Hussain 232102007

02 Muhammad Yousaf 232102008

CHAPTER 1: Final Year Proposal…………………………………………………………5

1.1 Project Title: …………………………………………………………………….…….5

1.2 Introduction: …………………………………………………………………….…….5
1.3 Goal: ……………………………….……………………………………………….……..5
1.4 The main objective of E-Commerce website………………..……..6
1.5 Back ground and justification…………………………………………………..6
1.6 Project Methodology……………………………………………………….………6
1.6.1 Searching in an easier way:……………………………………………………………………………………………7
1.6.2 Potential Student will no wait:……………………………………………………………………………….………7
1.6.3 Simplicity within the payment process:………………………………………………………………………….7
1.6.4 Security and reliability:…………………………………………………………………………………………………..7
1.6.5 Natural positioning within search engine:………………………………………………………………………8

1.7 Project Architecture:………………….………………………………………..…..8

1.8 Project Scope:…………………………………………………………………………..9
1.9 Exclusion:………………………………………………………………………………….9 1.10
Software Specifications:………………………….………………………………..9
Hardware Specification:……………………………………………………………………………………………..9

1.11 Tool and Technologies:…………………………………………..………………10

Chapter 2: First Deliverable....…………………………………………………..…….11

2.1 Project Feasibility report: …………….……………………………………….....11

2.1.1 Technical Feasibility: ……………………………………………………………………………………………………11

2.1.2 Economic Feasibility: …………………………………………………………………………………………………..12

2.1.3 Schedule Feasibility: ……………………………………………………………………………………………………12

2.1.4 Specification Feasibility: ……………………………………………………………………………………………..12

2.1.5 Operational Feasibility: …………………………………………………………………………………………….…13

2.1.6 Motivational Feasibility: ……………………………………………………………………………………………..13

2.1.7 Information Feasibility: ……………………………………………………………………………………………….13

2.2 Project Scope …………………………………………………………………..……….13

2.3 Project/Product costing: ………………………….……………………………….13

2.4 Project cost estimation by function point analysis: ……….………….14

2.5 Activity based costing: ………………………………………………………………14

2.6 Task dependencies table: ………………………………………………………….15

2.7 CPM- Critical Method: …………………………………….………………………..16

2.7.1 Draw the Network Table: ……………………………………………………………………………………………..16

2.7.2 Estimate Activity Complete Time: …………………………………………………………………………………17

2.8 Gantt Chart: ………………………………………………………………………………19

2.9 Task and Member Assignment Table: ……………….……………………..19

2.10 Tool and Technology with reasoning: ………………………………………19

2.11 Technology with Reasoning: …………………………………………………..20

2.12 Vision Document: …………………………………………………………………..20

Chapter 3: Second deliverable for object oriented approach: ………...21

3.1 Introduction: ……………………….……………………………………………………21

3.2 Organization chart: …………………………………………………………………..21

3.3 Scope of the System: ………………………………………………………………..22

3.4 Existing System: ……………………………………………………………………….22

3.5 Initial requirement: ………….……………………………………………………….23

3.6 External Entities: ....….………….………………………………………………….23

3.7 Capture shell statements: …….……………..……………………………..….. 24

3.8 Allocate Requirements: …………………………………………………………….24

3.9 Prioritize Requirements: ….……………………………………………………….25

3.10 Use case Diagram: ……….…………………………………………………………26

3.10.1 Use Case Description: …………….…………………………………………….28

3.11 Requirements Trace ability Matrix: …………………………………………30

Chapter 4 Third Deliverable for Object Oriented Approach: ………..…31

4.1 Domain Model: ….……………………………………………………………………..31

4.2 Sequence Diagram: …………………………………………………………………..32

4.3 Collaboration Diagram: …………………………………………………………….33

4.4 Design Class Diagram: ……………………………………………………………….35

4.5 State Chart Diagram: …………………………………………………………………36

Chapter 5 2nd and 3rd Deliverable for Structured Approach: …………..25

5.1 Introduction: ……………………..…………………………………………………….25

5.2 Entity Relationship diagram ……………………………………………………..26

5.3 Content level DFD: ………..………………………………………………………….27

5.4 State Transition Diagram: …………..…………………………………………….28 5.5

Architectural Design...……………………………………………………………….29

Chapter 6 4th Deliverable (User Interface Design)……………………………35

6.2 What was achieved:………………………………………………………………….30

6.3 Possible future improvements:………………………………………………….31

Chapter 1: Final Year Proposal
Pioneer Science College Portal is designed to provide essential services and information to
students, staff, and visitors in a smooth and efficient way. Our college portal helps users manage
academic tasks, access college resources, and communicate with college departments without
any problems. In Today fast-paced environment, saving time and solving issues quickly is crucial
and the Pioneer Science College Portal makes it Possible.

There are three main types of users in our system:

• Visitors: Individual who can view general information about the college.
• Students: Registered users who can access personalized resources like course
materials, announcements, and results.

• Admin/Staff: College employees who manage the portal, update

information, and assist students and visitors.

1.1. Project Title:

Online College Portal System
1.2. Introduction:
The Pioneer Science College Portal is web based platform designed to enhance the
academic and administrative processes of Pioneer Science College. This portal serves as a
centralized system for managing student’s records, announcements, results, attendance,
and communication between students, teachers, and administrative staff. With the
growing need for digital transformation in educational institutions, this portal aim to

bring automation, transparency, and ease of access to important college functions.

1.3. Goal:
To develop an Online Pioneer Science College Portal that provides effective and
transparent functionalities for managing all students’ registrations, inquires, and
submissions. The system is designed to maintain complete record of student admissions,
fee submission, course enrollments and academic activates. it also provides services such
 as online result checking, announcements and event updates for the convenience of

students and staff.

1.4. Main objective of online portal system:

The objective of this portal system is to design and implement user friendly portal that
bridges the communication gap between students, teachers and administrators.

• Provide a secure login system for admen, teachers, and students.

• Allowing teachers to upload results manage attendance, and post notices.

• Enabling students to view results, announcements and personal information.

• Giving administrators full control over the system’s operations.

1.5. Background and justifications:

When student and staff of Pioneer Science College need academic or administrative
assistance, trouble often arises when reliable information or support services are unavailable or
difficult to find. Our online portal system offers the most efficient and user friendly way to
access college related services and information’s. With just a single click, users can connect to
highly organize academic resources, administrative support, campus updates, and ensuring tasks
are complete on time.

Keeping this in mind, our proposed system serves as a centralized platform for all college
services, where processes of standardized and transparent, eliminating confusion or
inconsistency. Several aspects like admissions, course management, fee submission, notices, and
student queries are integrated into the system to create a supportive and organized college
environment that satisfied students, faculty, and staff.

1.6. Project Methodology:

There are various important factors that influence the success of an educational portal: how it
is easy for users to find the information or services they are looking for, how smoothly they can
complete tasks like registration, fee submission, and how quickly the system responds their
request. All these factors determine whether students, faculty, and staff will continue to use the

portal regularly.
 In general, users today are more impatient and expect fast, easy, and reliable service
without spending much time searching.

1.6.1. Searching in an Easier Way:

Our approach uses a customizable and efficient search system that helps new and
returning users find academic services, announcements, and resources quickly and
easily. We also integrate suggestion for related services, such as upcoming events or
important notices, to keep users engaged and informed.

1.6.2. Users Will Not Wait:

When users visit a website that loads slowly, they quickly lose their patients and leave.
Our portal ensures fast loading speed by using optimized style sheet (CSS) and
structured files. We also maintain strong server capabilities to handle high traffic during
admissions, exams, or other peak periods.

1.6.3. Simplicity within the task process:

We have invested significant effort into making all processes, such as registration, fee
payment, and application submissions, extremely simple and user friendly. Simplicity is
our main focus for all college services provided through the Pioneer Science College
Portal.

1.6.4. Security and Reliability:

Our system is trustworthy, secure, and user friendly, capable of handling high volume of
traffic efficiently. All sensitive transactions, including online fee payments, are processed
securely. The system is easy to integrate with existing administrative operations, helping to
reduce operational costs and improve overall efficiency.

1.6.5. Natural Positioning Within Search Engine:

Our portal is designed for simple and efficient browsing, where student, staff, and visitors
can easily find the information they need along with maintaining a strong and consistent
college brand image.
We have carefully built the Pioneer Science College Portal with best practices in web
development and search engines. Our experience with managing multiple educational
service projects has allowed us to adapt our skills effectively to meet the unique needs of
Pioneer Science College, ensuring maximum online visibility and accessibility.

1.7. Project Architecture:

 The project Architecture of the Pioneer Science College Portal consists of the following
modules:
• Course catalog:
Students are able to browse, search, and filter available academic programs,
courses and activities within a structured multi-level category system.
• Promotion & Visibility:
To enhance the college’s online presence and reputation, the portal is designed
with SEO (Search Engine Optimization) strategies, making it easier for
prospective students to discover and access information about Pioneer Science
College.
• Communication:
The portal facilitates effective communication between the administration,
current students, faculty, and prospective students through announcements,
messaging features and contact forms.

• Enrollment & Registration:

Students manage their academic journey by adding or dropping courses,
selecting subject modules, and completing the registration process, including
necessary form submission and fee payments.

• Academic Fulfillment:
All academic resources, including study materials, schedules, and online lecture
links, are delivered digitally through the portal to ensure easy access and
support for learning.
• Student Support:
The portal provides students with access to their personal profiles, academic
progress, enrollment status, fee payment record, exam schedules, and other
essential services. Students can also submit queries, feedback, and requests for
assistance directly through the platform.

1.8. Project Scope:

Our “Online College Portal System” is supposed to have the following features:
• Multi-role user access (Admin, Teacher, Student).
• Student registration and record management.
• Result publishing and notification system.
• Attendance tracking.
• Announcements and notices.
 • User-friendly dashboard for each role.
• Improve administrative efficiency and create an academic environment.

1.9. Exclusion:
A complete portal system can be including.

1.10. Software specification:

• 2GHz
• Maximum 1Gb ram

Hardware specification:
• Processor: x86 compatible processor
• RAM: 512 MB or greater
• Hard disk: 20 GB or greater
• Keyboard: 104 keys standard
• Mouse: 2/3 button. Optimal/Mechanical.

1.11. Tools and Technologies:

There are some technologies and tools:

Front End:
The languages that we will use to make front end:

• HTML (Hyper Text Markup Language)

• CSS (Cascading Style Sheet)
• JavaScript (JS)
Back End:
For back end we will use languages:

• PHP
• MY SQL

Tools:
• XAMPP
• Visual Studio

CHAPTER 2: FIRST DELIVERABLE

The first deliverable focuses on the planning and scheduling of the Pioneer Science College
Portal.

• Project feasibility
• Project Scope
• Project Costing
• Task dependency table
• Critical path method analysis
• Gantt Chat
• Introduction to team members
• Task and member assignment table
• Tool and technologies • Vision documentation

2.1 Project feasibility report:

Before beginning the development of Pioneer Science College Portal,it was crucial to assess its
feasibility across different aspects. The types of feasibilities analyzed include.

• Technical feasibility
• Operational feasibility
• Economic feasibility
• Schedule feasibility
 • Specification feasibility
• Information feasibility
• Motivational feasibility
• Legal and ethical feasibility

2.1.1. Technical feasibility:

The Pioneer Science College Portal is an educational management system that provides an
efficient platform for students, teaches, and administrators to interact and manage academic
activities. Student information, teacher details, and administrative data are securely stored in
backend database. The portal is developed using PHP and the backend language to handle all
HTML requests from users. With the integration of PHP, HTML, CSS, JavaScript, and a relational
database (like My SQL), the project is technically feasible and capable of meeting all functional
and non functional requirements.

2.1.2 Economic feasibility:

The economic feasibility plays a vital role in successful implementation of the Pioneer
Science College Portal.
For the development of the system, a reliable web hosting server will be purchased from
a professional service provider.
This server will ensure the smooth execution of the portal handling all user interactions,
data storage, and transactions efficiently. A benefit cost analysis justifies that the
investment in hosting, maintenance, and promotion is economically feasible considering
the long term advantages. To promote the portal and ensure its reach to all students and
staff different marketing strategies may be employed:
• Google Ads
• Local Advertisement campaigns • Newspapers and Media Publications

2.1.3. Schedule feasibility:

Time management is a crucial aspect during the development of the Pioneer Science College
Portal. This feasibility ensures that the portal will be completed within a specific timeline. The
estimated time to complete the project is three months. Each phase of the project is carefully
planned. For example, the requirements gathering phase is scheduled to be completed within 6
days, followed by design, development, testing, and development phases.

2.1.4. Specification feasibility:

Specification feasibility outlines the hardware and software requirements necessary for the
successful development and deployment of the portal. The minimum system specification for
this project is:

• RAM:1GB or higher
 • Processor:1GHz or faster, Compatible Processor
• Hard Disk:40 GB or more
These specifications ensure that the development and hosting environment can efficiently
support the systems requirements.

2.1.5. Operational feasibility:

The Pioneer Science College Portal will streamline the management of academic records,
admission processes, examination results, and other college related activities. The portal will
primarily be managed by the admin panel, allowing administrative staff to handle all students,
teachers, and event data in the centralized system. This platform significantly reduces the
burden of manual record keeping. Improving accuracy, efficiency, and accessibility

2.1.6. Motivational feasibility:

Nowadays, students and parents often seek quick access to educational services and updates.
This Portal provides easy and fast access to important information online without requiring
physical visits to the college. The system will also empower the college administration to make
informed decisions, manage admissions effectively, and enhance student engagement by
offering real time updates and services.

2.1.7. Information feasibility:

This portal designed to be user friendly and easy understandable by all users, including
students, parents, teachers, and administrative staff. All essential information such as
admissions details, examination results, announcements, events schedules, and faculty profile
will be accessible in an organized and clear format. This ensures user can quickly find and
interact with the information they need without confusion or time wastage.

2.2. Project scope:

Our “Online College Portal System” is supposed to have the following features:

• Multi-role user access (Admin, Teacher, Student).

• Student registration and record management.
• Result publishing and notification system.
• Attendance tracking.
• Announcements and notices.
• User-friendly dashboard for each role.
• Improve administrative efficiency and create an academic environment.
2.3. Project/ Product costing:
Cost estimation plays a vital role in the development of Pioneer Science College Portal. Most of
the work in cost estimation focuses on cost modeling, where cost is analyzed using
mathematical formulas and metrics to produce reliable estimates. The accuracy of these models
can be enhanced by calibrating them to the specific development environment, which involves
adjusting the weightings of the metrics according to project needs and conditions.

2.4 Project cost estimation by function point analysis:

Functional Point Analysis (FPA) provides a structured approach to measure the functionality
delivered by the portal. It also helps monitoring and controlling Scope Creep by allowing
comparisons of function points at various stages: requirements analysis, design, coding, testing,
and implementation. This analysis helps evaluate how accurately and efficiently the initial
project requirements was captured and communicated to the development team.
Function Low Average High Total

External Inputs 80 90 150 320

External Outputs 55 70 90 215

External Inquires 50 60 80 190

Internal logical files 45 50 70 165

External interface files 40 40 60 140

Total 1030

1030*0.4

Total adjusted 412

2.5 Activity based costing:

Activity based costing is another methodology used to accurately measure the cost of activities
and resourced assigned during the project. Recourses are first assigned to activities, and then
assigned to different part of the project based on their usage. This ensures more precise cost
control and management.

Activity Cost (PKR)

Feasibility Reports 15000
Cost estimation by function point analysis 7000
Activity Based Costing 7000

Critical path method 12000

Task dependency and duration 10000

Vision Document 5000

Risk list 25000

Allocation Requirements 14000

Design Interface 18000

Modeling 30000

Test and Evolution 25000

Improve Test 35000

Show results 20000

Total Cost 223000
2.6 Task dependencies table:
Task# Task Dependencies
T1 Proposal None
T2 Feasibility Report T1
T3 Cost Estimation T2
T4 System Specification T2
T5 Domain Model T1,T2
T6 Allocation Requirement None
T7 User T7
T8 Processor T7,T8
T9 Testing T9
T10 Application T4,T5
development
T11 Showing T7,T8,T9,T10

2.7 CPM- Critical Method:

CPM provides the following benefits:
Provides a graphical view of Project
Predicts the time required to complete the project.
Shows which activities are critical to maintain the schedule and which are not.

Specify the Individual Activities:

Individual Activities are as follow:
• Planning
• Analysis
• Logical Design
• Physical Design
• Testing
• Implementation
Determine the sequence of the activities:
All activities are dependent n each other like, first planning and then go to second
activity which is name as analysis and then logical designing after it physical designing,
than testing it all and then deployment.

2.7.1 Draw the Network Table:

Task Activity Predecessor Duration
Proposal A None 20
Feasibility Report B A 12
Cost Estimation C B,A 25
System Specification D C 30
Analysis E D 20
Allocation Requirement F E 15
Application development G F 35
Processor H G 35
Testing I H 20
Deployment J I 19

20 12
 • 20A B

30 20
25

C D E

35 15

G F

19
35 20

H I J

2.7.2 Estimate Activity Complete Time:

Task Duration ES EF LS LF TS
Proposal 15 0 20 0 20 0
Feasibility Report 07 20 32 8 20 12
Cost Estimation 25 20 45 20 45 0
System Specification 15 45 75 45 75 2
Analysis 10 75 95 75 95 0
Allocation Requirement 10 95 110 95 110 6
Application development 30 110 145 110 145 20
Processor 30 145 180 145 180 0
Testing 15 180 200 180 200 3
Deployment 14 200 219 200 219 0
180 20 200 200 19 219

I J

180 20 200 200 19 219

 2.8 Gantt Chart:
The Gantt chart is one of the most popular scheduling tools in project management. It’s a
horizontal bar chart that shows progress on a project schedule. Tasks are arrayed on the vertical
axis while the horizontal axis represents time.
ID Task name 3 Jan 8 Jan 14 Jan 19 Jan 25 Jan

1 Planning

2 Analysis

3 Design

4 Coding

5 Testing

6 Deployment

2.9 Task and Member Assignment Table:

Member Name Task Assigned Skills
Yasir Mumtaz Requirements gathering. HTML
Feasibility Study. CSS
Modules linking. JavaScript
Web development. PHP
Documentation.
Akamal Farooq Testing and Quality Assurance. HTML
Deployment. CSS
Requirement Analysis. JavaScript
Risk Assessment. PHP
SQL
2.10 Tool and Technology with reasoning:
Language Reason
HTML Fronted Development
CSS Designing
Java Scrip Dynamic interface
SQL For database
PHP Backend development

2.11 Technology with Reasoning:

HTML:
HTML is widely used to view and display the contents browser XML is used to carry the data
while on other hand HTML is used in this project to develop the frontend.

CSS:
CSS is used to style the front end of the Web Page.

Java Scrip:
It is used to make the web page more interactive.

SQL:
Structure Query Language is used to create, view, delete, and update data which is stored in a
Database.

PHP:
It is a backend language widely used in making MCV to create dynamic web pages. It is a
scripting language.
2.12 Vision Document:
The Vision Document Serves as the foundation for the development of Pioneer Science College
Portal. It is primary deliverable during the initial planning phase and plays a key role in guiding
the project into more detailed stages of development. The purpose of this document is to
ensure all stakeholders share a common understanding of the portal’s goals and scope. The
vision document captures core requirements and constraints offering readers an early
understanding of the system’s structure, features and purpose within the academic
environment of Pioneer Science College.

Chapter 3: Second deliverable for object

oriented approach
3.1. Introduction:
Pioneer Science College Portal is a highly useful platform for students, faculty, and
administrative staff who need access to college-related services such as admissions, result
checking, timetable viewing, notices, and student record management. In today's fastpaced
 world, everyone wants to save time and access services conveniently and without hassle.
Therefore, an online college portal is extremely beneficial for both students and staff. The
admin and faculty members play a crucial role within the project they can register and
manage content through the portal. Users (students) can also view available college
services and resources.

The Pioneer Science College Portal consists of multiple modules. Students in need of
services can register on the portal and access various academic features such as exam
results, attendance records, and class schedules. They can submit details through forms
such as name, email, phone, and registration number which are stored in the database for
future reference. This allows faculty and administration to efficiently manage student data
and respond to inquiries. When students or staff needs academic support, delays often
occur due to lack of proper communication or inaccessible information. Our online portal
offers the most efficient way to manage academic tasks. With just a few clicks, users can
interact with college systems, access important updates, and stay informed.

3.2. Organization chart:

The organizational chart plays a vital role in providing a clear overview of the college's
functional areas and their division into various departments. It helps users, especially.

3.3. Scope of the System:

The system will be utilized by Pioneer Science College. The end user of the system is the admin,
who will have full access to manage the portal. The admin will be able to add new students,
teachers, notices, and academic data, as well as update or remove existing records. The admin will
also manage the details of courses, events, and services offered by the college.

• To provide a centralized platform where students, parents, and staff can view all academic and
administrative information with a single click.
• Provide clear and standardized information regarding college fees, courses, and services.
• Display all necessary academic and administrative details online for easy access by students and
staff.
• As a web-based system, it allows students to register online, view course details, results, and
important announcements.
• A student request system (similar to a shopping cart) will help users apply for admissions, register
for courses, or request certificates easily.
• When a student wants to register for a course or service, they can select it, add it to their request
list (basket), and proceed to submit it through an easy checkout-like process.

3.4. Existing System:

Many educational institutions still rely on manual systems. This existing method causes
numerous issues such as data redundancy, inconsistency, and excessive paperwork, which
results in wasted time and resources. Some major drawbacks include:

• Difficulty in maintaining personal and academic information.

• Risk of documents being misplaced or lost.
• Physical files and cabinets take up a lot of space.
• Excessive paperwork leads to duplication and errors in data.
• Searching and managing student or academic records is slow and inefficient.

Keeping these limitations in mind, we aim to develop a user-friendly Pioneer Science

College Portal that addresses these problems effectively.

The portal operates at two primary levels: Admin Level and User Level.

• Admin: can register students and faculty, manage academic records, post
announcements, upload course materials, and handle feedback.
• Users: (students/parents/faculty) can register and log in to the portal to perform various
actions such as viewing course lists, checking results, accessing notices, downloading
Materials, and providing feedback.

3.5. Initial Requirements:

1. Admin registration functionality.

2. Admin can securely log in to the system.

3. Admin can manage academic and portal services.

4. Admin can add, update, and delete various content modules (such as
notices, student data, faculty details, etc.).

This system is specifically designed for Pioneer Science College. The end user of the portal is
the admin, who will have full access and control over all system functionalities.

1. Admin Access and User Access:

Access to the Pioneer Science College Portal is restricted to registered users, each with
designated access levels. Individuals must first submit a registration request, providing their
personal information such as name, email, contact number, and desired role (e.g., student,
faculty).

All registration requests are reviewed by the Admin, who has the authority to accept, reject,
or temporarily hold these requests based on the authenticity of the provided credentials. Users
may also request to update their profile or records, including details like contact info, academic
data, or other relevant submissions.

Once approved, registered users can log in and access their personal dashboards where they
can:

• View their personal details and academic records.

• Track submitted queries or feedback.
• Request changes or report issues. ➢ Similarly, the Admin can:
• Search for any user record.
• View a complete list of currently registered students, faculty, or staff.
• Manage profile updates and submitted feedback.
3.6. External Entities:
Admin: The primary user of the system with full control over portal functionalities. The
admin manages user registrations, academic content, staff and student records, notices, and
system operations.

Student: Students can register through the portal, view their academic profiles, submit
queries or feedback, and access college-related updates and information once approved by the
admin.

Faculty/Staff: Faculty and staff members can request access to the portal, view and
manage their profiles, contribute academic content if permitted, and communicate with the
admin through the system.

3.7. Capture shell statements:

Para# Initial Requirements
1.0 A student shall access the Home page.
1.0 An admin shall log in or register.
1.0 A student shall view academic and portal service information.
1.0 A student shall search for notices, results, or faculty information.
1.0 A student shall submit feedback or queries.
1.0 The system shall provide a user-friendly interface.
1.0 The system shall include a database to store user and academic data.
1.0 The system shall save data entered by the student or admin.
 1.0 The system shall allow the admin to add, delete, or update portal content.
1.0 The admin shall manage all system activities.
1.0 The admin shall manage student and faculty information.

3.8. Allocate Requirements:

Para# Initial Requirements Use Case Name
1.0 A student will request for Submit Admission form
admission.
1.0 A student registers in the Student Registration
portal.
1.0 A student logs into the portal. Student Login

1.0 System updates the student’s Update Student Information

submitted information.
1.0 System processes requests Change Academic Status
like upgrading semester or
program.
1.0 A student views his profile View Student Details
and academic details.
1.0 Admin or authorized users Search Student
search for a student details.
2.0 Both registered students and Submit Request
staff can submit different
requests (e.g. leave.
certificate, etc.).
2.0 Student can pay fees either Pay Fees
through cash or credit card.
2.0 System generates fee invoice, Generate Invoice
conformation slip, and
updates the records.
2.0 Users view the status of their Track Request Status
submitted forms or requests.

3.9. Prioritize Requirements:

Para# Rank Initial Use Case ID Use Case
Requirements Name
1.0 Highest A student will UC_1 UC Submit
apply for Admission
 admission into the
college.

1.0 Highest A student registers UC_2 UC Student

himself on the Registration
portal.
2.0 Highest Student can make UC_3 UC Pay College
payment either Fee
through cash or
Credit card.
2.0 Highest System will UC_4 UC Generate Fee
generate fee Invoice
invoice,
conformation,
receipt, and update
records.
2.0 Medium Both privileged UC_5 UC Submit
and registered Request
users can submit
online form.
1.0 Medium The system UC_6 UC Process
provides student Registration
registration Request
process.
1.0 Medium System updates the UC_11 UC Student
student’s request Request
or form.
1.0 Medium A student views UC_15 UC View
their personal or Student Details
academic details
1.0 Medium Admin can search UC_16 UC Search
for student details. Student
2.0 Medium Users view the UC_17 UC Track
status of submitted Request Status
forms or
applications.
2.0 Medium Student places a UC_19 UC Manage
request for Requests
cancellation of an
application or
form.
3.10. Use case Diagram:
The Use Case Diagram captures the core functionalities and system requirements of the
Pioneer Science College Portal by illustrating the interactions between users (actors) and the
system through defined use cases. These use cases represent high-level services that the portal
provides to its users, such as students, faculty, and administrators.

A use case is initiated by an actor with a specific goal, such as registering, submitting a
form, or checking academic progress. The interaction continues until the goal is achieved
successfully. These use cases reflect the steps required between the actor and the system to
fulfill a particular task, without focusing on internal processes or implementation details.

The use case diagram outlines what actions are performed by which actors and for what
purpose, making it easy to understand the expected behavior of the portal. A complete set of
use cases defines all possible interactions, thereby specifying the entire required behavior of the
Pioneer Science College Portal.

Administrator level:
Student Level:
 Schedule:

3.10.1. Use Case Description:

1. Student Registration
Use Case ID: 1

Pre-Condition: Portal is accessible.

Basic Flow: Student enters registration details (Name, Email, Password, etc.).

Alternative Flow: Registration form is not completed correctly or submission fails.

Post-Condition: Student is registered successfully in the system.

2. Admin Login
Use Case ID: 2

Pre-Condition: Admin account is already registered.

Basic Flow: Admin enters email and password.

Alternative Flow: Incorrect email or password entered.

Post-Condition: Admin is successfully logged in.

3. Manage Courses
Use Case ID: 3

Pre-Condition: Admin is logged in.

Basic Flow: Admin can view, add, edit, or delete courses offered by the college.

Post-Condition: Courses are managed successfully.

4. Assign Teachers
Use Case ID: 4

Pre-Condition: Courses and teachers exist in the system.

Basic Flow: Admin assigns teachers to specific subjects or courses.

Post-Condition: Teachers are assigned to respective subjects.

5. Teacher Login
Use Case ID: 5

Pre-Condition: Teacher is registered in the system.

Basic Flow: Teacher enters email and password to log in.

Alternative Flow: Incorrect email or password.

Post-Condition: Teacher is logged in successfully.

6. View Student Records (Accounts)

Use Case ID: 6
Pre-Condition: Student data has been entered.

Basic Flow: System fetches and displays student academic and fee records.

Alternative Flow: Data fetch failure due to technical issue.

Post-Condition: Student records displayed or updated in the database.

7. Logout:
Use Case ID: 7

Pre-Condition: User (Admin/Teacher/Student) is logged in.

Basic Flow: User logs out of the portal.

Alternative Flow: Logout process fails.

Post-Condition: User is logged out successfully.

3.11. Requirements Trace ability Matrix:

Use Case Use Pre Condition Basic Alternate Post Condition

Name Cas Flow s Flow
e ID
Student UC_ Portal is Student None Student
Registratio 1 accessible enter registered in
n registratio system
n details
Admin UC_ Admin must be Admin Incorrect Admin gains access
login 2 registered enters credentials to the admin
valid system dashboard
credential prompts
s error
Manage UC_ Admin is logged Admin can Failure to Record are
academic 3 in add, load or successfully man
records update, or update aged
remove records
student
academic
details.
 Course UC_ Courses/applicati Students Submission Course
enrollment 4 on are available submit failure or enrollment/applicat
course course ion on is recorded
enrollmen unavailabili
ts or ty
applicatio
ns
Faculty login UC_ Faculty is Faculty Incorrect Faculty is logged in
5 registered enters login
Email and credentials
password
Account UC_ Fee and record System Data Fee records are
manageme 6 data available retrieves retrieval shown or updated
nt and fails
display
student
fee status
from the
database
Logout UC_ Users is logged in Users clicks Logout fails Uses session is
7 logout ended successfully

Chapter 4

Third Deliverable for Object Oriented Approach

This deliverable focuses on the software design of the Pioneer Science College Portal. It
includes a detailed representation of how different components of the system interact and
behave. The following components are included in this phase:

• Domain Model
• System Sequence Diagram
• Collaboration Diagram
• Operation Contract
• State Transition Diagram
 • Sequence Diagram
• Data Model

4.1. Domain Model:

The domain model captures the essential requirements and elements of the Pioneer
Science College Portal. It outlines the core concepts, relationships, and behaviors that define the
system. This model helps in understanding the real-world structure of the application by
focusing on:

Features derived from the use cases of the portal.

• Clearly defined scope of the system.

• Behavioral characteristics of the system components.

Steps in Domain Modeling:

• Identify and illustrate important conceptual classes relevant to the college portal
(e.g., Student, Teacher, Course, Attendance, Results, etc.).
• Recognize domain objects based on real-world interactions within the college
environment.
• Define associations between these classes (e.g., A Teacher teaches many Courses;
A Student enrolls in multiple Subjects).
• Specify attributes for each class wherever applicable (e.g., Student has Name, Roll
Number, Class, etc.).
4.2. Sequence Diagram:
In the context of the Pioneer Science College Portal, a sequence diagram illustrates how
different components of the system (such as students, teachers, and administrators) interact
with each other through the exchange of messages over time. Objects in the diagram, such as
"Student," "Teacher," "Admin Panel," or "Login System," are shown as rectangles with the
underlined class names.

Activation:
Activation boxes in the diagram represent the duration during which an object (e.g., the
portal’s login system or registration form) is actively performing a task, such as validating user
credentials or storing data.

Life Line:
 Each object has a lifeline, represented as a vertical dashed line, indicating its existence
and participation in the interaction during a certain time frame.

Destroying Objects:
If a specific module or process in the portal ends early (such as a user session being
terminated), it is represented using an arrow labeled <<destroy>>.

Loops:
For repeated interactions—like a student viewing multiple announcements or marks—a
loop is illustrated as a rectangle. The exit condition (e.g., [no more announcements]) is shown at
the bottom-left in square brackets.

Object:
Objects such as "Student: User" or "Admin: User" are represented at the top of lifelines,
showing their role and class in an underlined format (e.g., student: User), indicating active
participation during the interaction.

Actors:
Actors like students, teachers, and administrators are the primary users of the portal and
are represented by the first lifeline in the diagram, initiating various interactions like login,
upload, or viewing content.

Messages:
Messages (shown as horizontal arrows) represent communication between components.
For example, a student sends a message to the login system with credentials, and the system
responds with success or failure.
4.3. Collaboration Diagram:
Collaboration diagrams in the Pioneer Science College Portal are used to illustrate how
various system components and users (such as students, teachers, and admins) interact to carry
out the behavior defined in specific use cases — for example, student registration, result
checking, or faculty login. These diagrams, along with sequence diagrams, help developers
understand and define the roles of each object involved in a particular interaction flow.

Objects:
In the portal, an object represents a system entity, such as Student: User, Admin: User,
or Course: Module. Each object is displayed with its name and class, underlined and separated

by a colon, like so: student1: Student Actors:

 Actors such as Student, Teacher, or Admin appear in the collaboration diagram as
initiators of interactions. For instance, a Student may initiate a request to view marks or register
for a course.

Links:
A link represents the communication path between two objects in the portal. These are
shown as solid lines and indicate how one object accesses or interacts with another, such as a
Student linked to a Course Module to register.

Message:
Messages are labeled arrows placed near links that describe the interaction or command
being passed. For example, a message likes 1: register Course () indicates that the student is
invoking the course registration function through the link to the course module.

4.4. Design Class Diagram:

4.5. State Chart Diagram:
A state machine is a useful tool for illustrating the different states that components of the
Pioneer Science College Portal can assume, along with the events or user actions that trigger transitions
between these states. This is especially helpful in describing dynamic behaviors of active modules within
the portal, such as user login, course registration, or result viewing. Implementing state machines is
essential for clearly defining and managing the behavior of interactive features in the portal.
Chapter 5

2nd and 3rd Deliverable for Structured Approach

5.1. Introduction:
The Analysis & Design Model for the structured development of the Pioneer Science
College Portal includes the following essential artifacts:

• Entity Relationship Diagram (ERD)

• Data Flow Diagram (DFD)

 • Architecture Design

• State Transition Diagram

5.2. Entity Relationship Diagram:

In the analysis model of the Pioneer Science College Portal, the Entity Relationship
Diagram (ERD) is used to understand the system’s structure by identifying entities and the
relationships between them. Each entity is defined along with its attributes, cardinality, and
modality.
Cardinality:
One Admin manages many Teachers.
Draw fully dressed ERD:
4.3. Context Level DFD:
The Context Level Data Flow Diagram (DFD) represents the Pioneer Science College
Portal as a single high-level process, displaying how it interacts with external entities such as
students, teachers, admin, and possibly parents or external organizations. It defines the overall
system boundaries and identifies the information exchanged between the system and its
environment.

Purpose:
This diagram gives a clear overview of the college portal’s environment by showing the external users
and systems that provide input to or receive output from the portal.

Steps in Building DFDs:

1. Build the Context Level:

Strata the flow of data between the system and each external entity

2. Create DFD Fragments for Each Scenario:

Break down each functional requirement or process (e.g., course registration, result
management, complaints submission) into individual DFD fragments.
3. Organize DFD Fragments into Level 1:
Combine related DFD fragments into a Level 1 DFD, which decomposes the single process

4.4. State Transition Diagram:

A State Transition Diagram (STD) is created to illustrate how the Pioneer Science College
Portal behaves in different situations. It helps to understand how the system responds to various
events and transitions between states.

Constructs of the STD:

State:
A condition or situation in which the Portal exists at a specific time, For example, Login Page,
Admin Dashboard, Student Panel, etc.

State Transition:
The movement from one state to another, For example, transitions from the Login Page to the
Student Dashboard after successful login.

Event:
An external or internal trigger that cause state, For instance, a student clicking the “Login”
button.

Action:
The operation that occur due to the transitions, for example, verifying login credentials or
loading student data

Guidelines for Developing the State Transition Diagram:

• List all possible states of the portal, such as Home Page, Login Page, Admin Panel,
Student Panel, Fee Submission Page, etc.
• Define how the portal transitions from one state to another based on specific user
interactions.
• Identify the events that trigger each state transition (e.g., login request, logout, form
submission).
• Determine the actions performed during each transition (e.g., data validation, user
authentication).
• Finally, draw a state transition diagram to visually represent these behaviors.
4.5. Architectural Design:
The focus of architectural design in the Pioneer Science College Portal is the mapping of
functional and non-functional requirements into well-structured software architecture. The Data
Flow Diagrams (DFDs) created during the analysis phase serve as the foundation for this design
process.

Two major structural design approaches are considered: Transform Flow Analysis and
Transaction Flow Analysis. These techniques help in identifying the overall system structure by
examining how data moves through the system and how user-initiated transactions are
processes.