Description
New Content for Week 4: System Development
Verbania has requested some functionality for the new social networking application. The following is a sample of the required functionality:
Explanation & Answer
Attached.
Outline
Introduction
Body
Conclusion
References
Running head: APPLICATION DESIGN
Application Design
Student’s Name
Name of Course
Instructor’s Name
1
APPLICATION DESIGN
2
Application Design
This section will majorly focus on the application’s design through which we are able to
visually demonstrate how the application functions during its implementation. We will, therefore,
use the Unified Modelling Language diagrams to illustrate how this is possible wherever
applications are developed or designed. The use case diagram, the class diagram, and the sequence
diagram will be used in the illustration of the desired application that Verbania would use in
running its business operations.
Sequence diagram
The sequence diagram gives a visual representation and control of functions in the system
right from the start of a session to a point where the user decides to log out of the system. With
respect to the diagram, the system requires a user to first create an account, log in and finally be
able to access the other functionalities of the system. Upon accessing the system and having made
APPLICATION DESIGN
3
a request to use the system, the user logs in and waits for the verification process that is carried
out by the database management system. The DBMS would ascertain whether the credentials are
correct or not after having determined whether the user is registered or he or she does not exist
completely (Dennis, Wixom, & Tegarden, 2015).
Wherever the credentials are wrong or the user is not registered, the system sends the user
back to the login or registration page to start the process afresh. Once the user is successfully
logged in, he or she would be able to access other functions in which he or she would add or
remove friends, create a profile, post comments and finally log out. Wherever the user intends to
edit the comments, the DBMS processes the comments and displays them on the blog section of
the system (Dennis et al. 2015). Every other process or function is invoked whenever the user
clicks on the desired functionality of the system.
Class diagram
APPLICATION DESIGN
4
The class diagram illustrates attributes the users exhibit when using a particular
information system or application. The class diagrams classify particular objects that usually have
the same attributes together in a single class that documents all the features the class contains
(Dennis et al. 2015). For instance, all users as illustrated above would be having similar attributes
that the system would want to capture some information about each of them.
The system would thus be required to capture the user’s name, username, the email address
and the password for purposes of authentication. The third partition of the class diagram illustrates
all the activities that a user would engage the system to carry out by invoking the specified
functions of the system. These functions include login and logout, posting comments, creating a
profile, adding and removing friends as well as registering. These functions thus give a reflection
of the specific processes that take place from the background in a particular information system in
a chronological manner. This, therefore, defines exactly what the user must expect wherever he or
she interacts with the system. Whatever you direct the system to do on your behalf is done exactly
as expected (Phang et al. 2015). You cannot invoke the registration method and get a posting
comments method.
Use case diagram
The use case diagram demonstrates the interaction that exists between the system and the
user. The user is able to register first before being allowed to log in to the ...