- Get link
- Other Apps
- Get link
- Other Apps
UML diagrams are used to describe the system architecture. UML 2.0 the specification provides thirteen kinds of diagrams. We suggest these diagrams:
Use case, Class, Data Flow, Sequence, Context, Component, and Collaboration
diagrams. This is motivated by the need to define a static representation of
the code and its runtime behavior. Listed diagrams are sufficient to fulfill
this purpose. To create UML diagrams, we use MS Visio tool.
Use case Diagram
A UML use case format is the main form of system/software necessities for a new software program underdeveloped. Use instances specify the anticipated behavior (what), and now not the exact technique of making it show up (how). Use instances as soon as special can be denoted each textual and visual illustration (i.e. use case diagram). Key thinking of use case modeling is that it helps us plan a device from the give up user's perspective. It is an advantageous method for speaking device behavior in the user's terms by using specifying all externally seen system behavior.
A use case graph is normally simple. It does now not show the detail of the use cases:
It only summarizes some of the relationships between use cases, actors, and systems.
It does no longer show the order in which steps are carried out to achieve the goals of each use case.
USECASE
NARRATIVES:
USE CASE NAME:
|
Login
|
USE CASE TYPE
|
|
USE CASE ID:
|
SPW01
|
Business Requirements: o
|
|
PRIORITY:
|
High
|
||
SOURCE:
|
System Design: þ
|
||
PRIMARY BUSINESS ACTOR
|
Students
|
||
PRIMARY SYSTEM ACTOR
|
Student Profile
(System)
|
||
DESCRIPTION:
|
This use –case describes the process by which user logs
into the system.
|
||
PRE-CONDITION:
|
Only those users can login who have own User Id and
Password which is given by System Manager after Registration in First
Semester.
|
||
TRIGGER:
|
When user clicks on the login button on the home page.
|
||
TYPICAL COURSE
|
|||
OF EVENTS:
|
Step 1: The user clicks on the login button.
|
Step 2: The system responds by displaying login form.
|
|
Step 3: The user fills the User ID and Password.
|
Step 4: System will validate the User Id and Password from
the database.
|
||
ALTERNATE COURSES:
|
Alt Step 4: System will display error message if the user
name and password does not match. System will show you these messages:
Incorrect user name
Incorrect password
|
||
CONCLUSION:
|
This use case concludes when the student successfully logs
in Student Profile.
|
||
POST-CONDITION:
|
User will have permission to access the student profile
|
||
ASSUMPTIONS:
|
Each user must have an data on the system.
User name and password should be validated by the system
|
VIEW STUDENT PROFILE:
USE CASE NAME:
|
View Student Profile
|
USE
CASE TYPE
|
|
USE CASE ID:
|
SPW02
|
Business
Requirements: o
|
|
PRIORITY:
|
High
|
||
SOURCE:
|
System
Design: þ
|
||
PRIMARY BUSINESS ACTOR
|
Students
|
||
PRIMARY SYSTEM ACTOR
|
Student Profile (System)
|
||
DESCRIPTION:
|
This use –case describes the
process by which student view his/her Personal Information.
|
||
PRE-CONDITION:
|
The user must have own User ID
& Password.
|
||
TRIGGER:
|
When user clicks on the
Personal Information in Menu bar on the home page.
|
||
TYPICAL COURSE
|
Actor Action
|
System Response
|
|
OF EVENTS:
|
Step 1: User will select
Personal Information on Home Page
|
Step 2: System will respond to
show Personal Information Page Successfully.
|
|
ALTERNATE COURSES:
|
|||
CONCLUSION:
|
This use case will conclude
when student view his/her own Personal Information.
|
USE CASE NAME:
|
View Previous Registered
Courses
|
USE
CASE TYPE
|
|
USE CASE ID:
|
SPW03
|
Business
Requirements: o
|
|
PRIORITY:
|
High
|
||
SOURCE:
|
System
Design: þ
|
||
PRIMARY BUSINESS ACTOR
|
Students
|
||
PRIMARY SYSTEM ACTOR
|
Student Profile (System)
|
||
DESCRIPTION:
|
This use –case describes the process
by which student view his/her Previous Registered Courses.
|
||
PRE-CONDITION:
|
The user must have own User ID
& Password.
|
||
TRIGGER:
|
When user clicks on the Course
Registration in Menu bar on the home page. First It shows all Previous
Registered Courses.
|
||
TYPICAL COURSE
|
Actor Action
|
System Response
|
|
OF EVENTS:
|
Step 1: User will select
Course Registration on Home Page
|
Step 2: System will respond to
show Course Registration Page Successfully.
|
|
ALTERNATE COURSES:
|
|||
CONCLUSION:
|
This use case will conclude
when student view his/her all Previous Registered Courses.
|
REGISTERED NEW
COURSES:
USE CASE NAME:
|
Registered New Courses
|
USE
CASE TYPE
|
|
USE CASE ID:
|
SPW04
|
Business
Requirements: o
|
|
PRIORITY:
|
High
|
||
SOURCE:
|
System
Design: þ
|
||
PRIMARY BUSINESS ACTOR
|
Students
|
||
PRIMARY SYSTEM ACTOR
|
Student Profile (System)
|
||
DESCRIPTION:
|
This use –case describes the
process by which student registered New Courses. And also predict their CGPA
of next semester.
|
||
PRE-CONDITION:
|
The user must have own User ID
& Password.
|
||
TRIGGER:
|
When user clicks on the
Registered New Courses on the Course Registration page, It shows all Offer
Courses. First user Registered Courses
then user predict Cgpa.
|
||
TYPICAL COURSE
|
Actor Action
|
System Response
|
|
OF EVENTS:
|
Step 1: User will select New
Registered Courses on Course Registration Page.
Step 3: User Select the
courses for registration. And click on the registered button.
Step 5: After that User
Predict GPA against registered courses.
|
Step 2: System will respond to
show all Offer Courses Successfully.
Step 4: System will save
registered courses in database.
Step 6: System will show predict gpa with
the help of history of student.
|
|
ALTERNATE COURSES:
|
|||
CONCLUSION:
|
This use case will conclude
when student registered new courses and also view his/her Predict CGPA of
Registered Courses.
|
USE CASE NAME:
|
View Predict CGPA
|
USE
CASE TYPE
|
|
USE CASE ID:
|
SPW05
|
Business
Requirements: o
|
|
PRIORITY:
|
High
|
||
SOURCE:
|
System
Design: þ
|
||
PRIMARY BUSINESS ACTOR
|
Students
|
||
PRIMARY SYSTEM ACTOR
|
Student Profile (System)
|
||
DESCRIPTION:
|
This use –case describes the
process by which student registered New Courses. And also predict their CGPA
of next semester.
|
||
PRE-CONDITION:
|
The user must have own User ID
& Password.
|
||
TRIGGER:
|
When user clicks on the
Registered New Courses on the Course Registration page, It shows all Offer
Courses. First user Registered Courses then user predict cgpa.
|
||
TYPICAL COURSE
|
Actor Action
|
System Response
|
|
OF EVENTS:
|
Step 1: User will select New
Registered Courses on Course Registration Page.
Step 3: User Select the
courses for registration. And click on the registered button.
Step 5: After that User
Predict GPA against registered courses.
|
Step 2: System will respond to
show all Offer Courses Successfully.
Step 4: System will save
registered courses in database.
Step 6: System will show predict gpa with
the help of history of student.
|
|
ALTERNATE COURSES:
|
|||
CONCLUSION:
|
This use case will conclude
when student view his/her Predict CGPA of Registered Courses.
|
RESULT
USE CASE NAME:
|
View Result
|
USE
CASE TYPE
|
|
USE CASE ID:
|
SPW06
|
Business
Requirements: o
|
|
PRIORITY:
|
High
|
||
SOURCE:
|
System
Design: þ
|
||
PRIMARY BUSINESS ACTOR
|
Students
|
||
PRIMARY SYSTEM ACTOR
|
Student Profile (System)
|
||
DESCRIPTION:
|
This use –case describes the
process by which student view his/her Current and Previous Result
|
||
PRE-CONDITION:
|
The user must have own User ID
& Password.
|
||
TRIGGER:
|
When user clicks on the Result
in menu bar on the Home page, It shows
all Previous Results and also Current Result.
|
||
TYPICAL COURSE
|
Actor Action
|
System Response
|
|
OF EVENTS:
|
Step 1: User will select
Result on Home Page.
Step 3: User Select the
Previous Result.
Step 5: User Select the
Current Result.
|
Step 2: System will respond to
show Result Page Successfully.
Step 4: System will show all
previous result
Step 6: System will show all
Current Result
|
|
ALTERNATE COURSES:
|
|||
CONCLUSION:
|
This use case will conclude
when student view his/her Predict CGPA of Registered Courses.
|
Sequence Diagram
UML Sequence Diagrams are interplay diagrams that detail how operations are carried out. They seize the interaction between objects in the context of a collaboration. Sequence Diagrams are time focus and they exhibit the order of the interaction visually by the use of the vertical axis of the layout to symbolize time what messages are despatched and when.
Data Flow Diagram
Also recognized as DFD, Data flow diagrams are used to graphically signify the drift of records in a business information system. DFD describes the approaches that are concerned in a device to switch information from the input to the file storage and reports generation.
Data go with the flow diagrams can be divided into logical and physical. The logical facts glide layout describes waft of data through a gadget to operate certain performance of a business. The physical records go with the flow diagram describes the implementation of the logical facts flow.
Data go with the flow diagrams can be divided into logical and physical. The logical facts glide layout describes waft of data through a gadget to operate certain performance of a business. The physical records go with the flow diagram describes the implementation of the logical facts flow.
Context
Diagram
Black Box Testing
Black-box test
design treats the system as a "black-box", so it doesn't explicitly
use knowledge of the internal structure. Black-box test design is usually
described as focusing on testing functional requirements. Synonyms for black-box include behavioral, functional,
opaque-box, and closed-box.
S.No
|
Test Condition
|
Expected Outcome
|
Evaluated Output
(Pass/Fail)
|
1
|
Does
the system use a consistent layout on every form?
|
Consistent
Layout across all forms
|
Pass
|
2
|
Does
the main form clearly identify the system’s purpose?
|
A
concise purpose statement on the main form
|
Fail
|
3
|
Does
the project use familiar names and terms?
|
Easy
to understand terms are used
|
Pass
|
4
|
Does
your project use consistent navigation?
|
A
consistent navigation via tab control
|
Pass
|
5
|
Does
the project reasonably limit the number of navigation items in a single
group?
|
Logical
grouping of navigation items
|
Pass
|
6
|
Do
all pages on the project contain navigational options?
|
A
global site menu that is consistent across all pages
|
Pass
|
7
|
Do
the pages form correctly?
|
Forms
are adjusted as controls are re sized
|
Pass
|
8
|
Does
every form on the site have a meaningful form title?
|
Concise
and meaningful form titles
|
Pass
|
9
|
Do
your forms have a consistently quick download?
|
Pages
load quickly
|
Pass
|
10
|
Is
the content on your site appropriately conversational?
|
Easy
to comprehend content
|
Pass
|
12
|
Are
the text and labels on your form sequentially arranged?
|
Consistent
layout for controls within a form
|
Pass
|
13
|
Is
your project accessible without a mouse?
|
Fail
|
|
14
|
Are
the tables on your site properly formatted?
|
Properly
formatted tables
|
Pass
|
15
|
Are controls aligned?
|
Aligned
Controls
|
Pass
|
16
|
Do the controls work correctly?
|
Controls
function properly
|
Pass
|
17
|
Have you used the correct and consistent color for
background?
|
Correct
and consistent color for general screen background
|
Pass
|
18
|
Is the color used for field consistent and
suitable?
|
Suitable
and decent field color
|
Pass
|
19
|
Are the background color fields a consistent one?
|
Field backgrounds the correct color
|
Pass
|
20
|
Is consistency being maintained while using
colors?
|
Consistency in using colors
|
Pass
|
21
|
Is the font style consistent throughout the
project?
|
Consistency
in using font styles
|
Pass
|
22
|
Are scrollbars being overused?
|
No
excessive use
|
Pass
|
23
|
Is the space on the page being properly utilized?
|
Wastage
of Space on Page
|
Pass
|
24
|
Easy to use actions?
|
Are
the actions easy to remember and to invoke
|
Pass
|
25
|
Too many actions?
|
No usage of too many actions
|
Pass
|
26
|
Are appropriate error messages being displayed
|
Appropriate Error messages are displayed.
|
Pass
|
Conclusion
These are some of the fundamental points regarding Black container checking out and the overview of its strategies and techniques. As it isn't possible to check the whole lot with human involvement with 100 percent accuracy, if the above-mentioned strategies and methods are used successfully it will truly enhance the first-class of the device. To conclude, this is a totally helpful technique to verify the capability of the device and identify most of the defects.
Hi, I'm Hifsah Nazish
Full-time blogger, podcaster and side project. Join me here, on
<script type="text/javascript" src="https://platform.linkedin.com/badges/js/profile.js" async defer></script>
|
- Get link
- Other Apps
Comments
Creately Data flow diagram tool allows you to model how information flows through systems. Also with the new features, you can add data to the shape which represents systems, and visualize a more informed process. It has custom shape libraries to showcase entities and easy tools to draw multi-level DFD diagrams.