Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
TMA application android design
Typology: Study Guides, Projects, Research
1 / 18
This page cannot be seen from the preview
Don't miss anything!
By RAHEEM ULLAH (CS120162098, [email protected]) MUBASHIR KHAN (CS120162078, [email protected]) MUHAMMAD NAWAZ (CS120162087, [email protected])
Dr. Muhammad Muneer Umar Institute of Computing KUST, Kohat
Signature
interacts with the system. It is also some types of use cases in the system where and how should be used by the particular user. A use case is a list of steps, typically defining interaction between a role (known in UML as “actor”) and a system, to achieve a goal. The actor can be a human being or an external system. The following is the Use Case Diagram of our system. Figure 4. 1 – Use Case Diagram of whole system Actor Super Admin Precondition The Admin needs to Login. Post-Condition Admin logged in successfully. Basic Flow The Super Admin wants to login to the system and enters his login username and password in the system and authenticated and logs in successfully to admin dashboard.
Main success scenario After successful login CRUD Operations: Admin can approve builder account and manipulate their accounts i.e. Roles assigning etc. Business Process CRUD Operations: Admin can close/ block account of customer or builder if they violate rules or term and conduction. Admin can create roles according to organizational management system. Alternative Flow (Exceptional Case) An Administrator will be login to system by giving its username and password, if the username and password are correct he will be on his own menu. If username or password is incorrect, the system will display the error message. Table 4. 1 - Use case for super admin authorities Table 4. 2 – Use case for Customer login and authorities Actor Builder Precondition Visitors need to give the correct URL (address) of this web application in the browser websites address bar. The builder needs to Login. Post-Condition Builder logged in successfully.
Basic Flow A visitor need any kind of information from this web application he/she will open his/her browser and will search for this web application either in his/her web browser address bar or Google after that if the address is correct then this web application main page will open for him/her. Main success scenario After browsing web application main page View main webpage Can search list of builder After successful login Can post for relative builder Chat with them and can deal with them Can received building maps and material cost estimate. Can receive legal construction documents from them and sign term and conduction. Can pay to builder. After the successfully of project can give a feedback to builder. Alternative Flow (Exceptional Case) Server down Internet problems Wrong address for this web application error 404 not found Old browser display content issue Invalid username or password Table 4. 3 - Use case for Customer and their facilities
Activity diagram is an important diagram in UML which describes the dynamic action of the system. Activity diagram is basically a flowchart which represents the flow of activities from one activity to another activity. The activity should describe the operations of the system. The flow is drawn from one operation to another and so on. Activity diagram may be used to detail situations where the parallel processes should occur in the execution of some activities. Following is the Activity diagram of our system which is fully explaining our proposed system. Figure 4. 2 – Activity diagram of Admin.
Figure 4. 3 – Activity Diagram of Customer and Builder.
Table 4. 4 – Activity diagram of Admin. Purpose: Role of Admin in Activity diagram Summary: When Admin visit the application main webpage he can be do the following business process: Decide himself as a Admin Authentication himself
After the successfully login found account dashboard. Now he can do parallel activity, can give an approval to builder or can close / block account of builder or customer if they break the rules of organization. Table 4. 5 – Activity diagram of Customer and Builder. Purpose: Communication and deal between Customer and Builder in Activity diagram Summary: When Customer and Builder visit the application main webpage they can be do the following business process: Customer: Decide himself is customer Create account. Authentication himself After the successfully login found account dashboard. Customer can search relative builders and see their profile. He can post a job. He can chat with builder and share his/her expression and documents which is relative with project. He cans payment to builder. In the end customer can feedback to the builder. Builder: Decide himself as a builder Create account which is going to admin for approval. Authentication himself After the successfully login found account dashboard. Builder can receive a post from customer. Can calculate material and labor cost for customer. Can share maps and material cost document with customer. Can receive a payment from customer. At the end can take feedback from customer. Table 4. 6 - Activity diagram of whole system. Purpose: (^) Function of Whole system Summary: When actors visit the application main webpage they can be do the following business process: Admin:
Model high-level interaction in a system between active objects Design the interaction of object instances in a partnership that makes use of a case Model the interaction of objects in a partnership that performs an activity A pattern of generic interactions (showing all possible paths through interaction) or unique intera ction instances (showing only one path through interaction)
Type of function of a person communicating with the subject matter Represents the functions of human users, external equipment or other topics. Lifeline A lifeline reflects the connection with an individual person.
The period during which an element performs an operation is represented by a thin rectangle on a lifeline. The top and bottom of the rectangle are in line with the initiation and completion date.
A message describes an interaction's basic contact between Lifelines. Call message is a kind of message that is an activation of goal lifeline service.
A message describes an interaction's basic contact between Lifelines. Return message is a type of message that reflects the transfer of information back to a corresponding previous message sender. Figure 4. 5 – Sequence diagram of Authentication.
Figure 4. 6 – Sequence diagram of Customer and Builder process.
An ERD used for the graphical representation of the conceptual database design. A high-level computational data model diagram is the ER or (Entity Relational Model). Entity- relationship model is based on the notion and relationship between real-world entities. Modeling ER helps you to systematically analyze data requirements to create a well-designed database. Object relationship diagram shows the object collection relationships contained in a database. In other words, ER diagrams will help you describe the logical database structure. With an ERD data model, it becomes easier to design the database, at the first place, and secondly it is easier to understand later.
This model is based on three fundamental concepts: Entities Attribute Relationship Entities: Entity is real world object which is exists in reality and represented it in database. It may be name, place, things and concepts. We store data in DBMS in the form of a table containing entity type information such as students, admin, teachers, customer, employees, builder, etc. Entity have sub divide in two types strong entity and weak entity. Attributer: The properties of Entity is called attributes Relationship:
