For complete guidance: Visit the link: https://youtu.

be/PQH6qwgwirA

<Automated Content Submission Evaluation System >

Version 1.0

Group Id: <S25PROJECTA8F21 >

Supervisor Name :< Adnan Asif>

Content
Submission
Evaluation System
 Table of Contents

1. Introduction of Design Document

2. Entity Relationship Diagram (ERD)

3. Sequence Diagrams

4. Architecture Design Diagram

5. Class Diagram

6. Database Design

7. Interface Design

8. Test Cases
1. Introduction of Design Document

The design document presented here serves as a comprehensive blueprint for the development of
the software system and includes several critical components essential for both implementation
and future maintenance. It begins with the Entity Relationship Diagram (ERD), which visually
represents the database structure, showing entities, their attributes, and the relationships among
them. This aids developers and database administrators in understanding how data will be stored,
accessed, and managed. Following the ERD, the Sequence Diagram illustrates the flow of
messages and interactions between various system components or objects over time. This helps
in clarifying how specific features or processes will function in a dynamic context, especially in
scenarios involving user actions or system triggers.

The Architecture Design Diagram outlines the high-level structure of the system, including the
division into layers or components such as the presentation layer, business logic, and data access
layer. This diagram supports decision-making around scalability, security, and performance. The
Class Diagram further defines the structure of the system by detailing the classes, their
attributes, methods, and the relationships between them, forming the basis for the object-oriented
design and ensuring consistency in the implementation phase.

The Database Design section expands upon the ERD by including detailed schema definitions,
table structures, and keys, which are crucial for efficient data storage and retrieval. The
Interface Design covers the layout and flow of user interfaces, ensuring user experience is
intuitive and functional. Wireframes, mockups, or prototypes may be included to visually depict
how users will interact with the system.

Finally, the document includes Test Cases, which specify the conditions under which the system
will be tested to verify that all components function correctly and meet the requirements. These
test cases play a vital role in quality assurance and help in identifying bugs early in the
development process.

The purpose of this design phase is to create a clear and detailed roadmap for developers, testers,
and stakeholders, reducing ambiguity and minimizing the risk of errors during implementation. It
ensures that all team members share a unified understanding of the system and its components,
leading to better project planning, resource management, and effective communication.
Ultimately, this phase lays the foundation for building a reliable, scalable, and maintainable
software system that aligns with the client's needs and expectations.
2. Entity Relationship Diagram (ERD) (To be developed using Microsoft Visio or

any other drawing software of your choice)

3. Sequence Diagrams (To be developed using Rational Rose or any other drawing

software of your choice)

A three-tier application architecture is a modular client-server architecture that

consists of a presentation tier, an application tier and a data tier. The data tier stores

information, the application tier handles logic and the presentation tier is a
graphical user interface that communicates with the other two tiers. The three tiers

are logical, not physical and might or might not run on the same physical server.

A three-tier architecture consists of the user interface, data processing tier and data

storage tier.

The logical tiers of a 3-tier application architecture

Presentation tier. This tier, which is built with HTML5, cascading style sheets and

JavaScript, is deployed to a computing device through a web browser or a web-

based application. The presentation tier communicates with the other tiers through

application programming interface calls.

Application tier. The application tier, which may also be referred to as the logic

tier, is written in a programming language such as Java and contains the business

logic that supports the application's core functions. The underlying application tier
can either be hosted on distributed servers in the cloud or on a dedicated in-house

server, depending on how much processing power the application requires.

Data tier. The data tier consists of a database and a program for managing read and

write access to a database. This tier may also be referred to as the storage tier and

can be hosted on-premises or in the cloud. Popular database systems for managing

read/write access include MySQL, PostgreSQL, Microsoft SQL Server and

MongoDB.

Benefits of a 3-tier app architecture

The benefits of using a three-tier application architecture include improved

horizontal scalability, performance and availability. With three tiers, each part can

be developed concurrently by a different team of programmers coding in different

languages from the other tier developers. Because the programming for a tier can

be changed or relocated without affecting the other tiers, the three-tier model
makes it easier for an enterprise or software packager to continually evolve an

application as new needs and opportunities arise. Existing applications or critical

parts can be permanently or temporarily retained and encapsulated within the new

tier of which it becomes a component.

Three-tier application programs might also be referred to as n-tier programs. In this

context, the letter n stands for "a number of tiers."

5. Class Diagram
6. Database Design

7. Interface Design
 8. Test Cases

Test
Case Description Input Expectation Output Pass/Fail Tested By
ID
Register Name, Email, Phone, User is created
TC- User added to DB
Team Password, and redirected QA Tester
001 and redirected
Member Role=TeamMember to dashboard
Evaluator is
Name, Email,
TC- Register added and Evaluator profile
Qualification, QA Tester
002 Evaluator awaits admin stored
Experience
approval
Login with
TC- Valid Email and Successful Role-based
valid QA Tester
003 Password login dashboard shown
credentials
 Test
Case Description Input Expectation Output Pass/Fail Tested By
ID
Login with Show error
TC- Wrong Error message
invalid "Invalid Pass QA Tester
004 Email/Password shown
credentials credentials"
Team
TC- User added to Member listed in
member joins team_id, user_id Pass Developer
005 team team
a team
TC- Assign team user_id, Team lead
Role updated Pass Developer
006 lead isTeamLead=True marked
video_link, topic, Entry created in
TC- Submit new
outcomes, description, Video stored VideoSubmissions Pass QA Tester
007 video
team_id table
Edit video
TC- Updated video link, Previous video Updated data
before Pass QA Tester
008 topic, outcomes updated reflected
deadline
Admin Evaluator
TC- Evaluator marked as
approves evaluator_id status = Pass Admin
009 approved
evaluator approved
Admin
TC- submission_id, Evaluator Submission mapped
assigns Pass Admin
010 evaluator_id assigned to evaluator
evaluator
Evaluator Scores
TC- Scores for all 10 Entry in Evaluations
submits recorded, total Pass Evaluator
011 criteria with total score
scores calculated
Evaluator
TC- Feedback Feedback linked to
adds Comments text Pass Evaluator
012 saved evaluation
comments
TC- Calculate Scores from all Average Leaderboard with
Pass System
013 leaderboard evaluators calculated rankings generated
Results are
TC- Publish
Trigger result publish shown to Results page visible Pass Admin
014 results
participants
TC- Send chat Message from team Chat displayed on Team
Message saved Pass
015 message member support side Member
Support
TC- Response sent Chat appears on Support
replies to Reply from support Pass
016 to user user interface Team
chat
View
Scores and
TC- feedback Feedback section Team
user_id, team_id comments Pass
017 from displays evaluations Member
shown
evaluator
TC- Submit Non-URL format Error message Validation failed Pass QA Tester
018 invalid video (e.g., text) "Invalid URL"
 Test
Case Description Input Expectation Output Pass/Fail Tested By
ID
link
Leave
TC- Empty topic or Prevent form Form highlights
required Pass QA Tester
019 outcomes submission required fields
fields blank
Session ends,
TC- Logout user
Click logout button return to login Redirected to login Pass QA Tester
020 session
screen