CIS510 Discussion Reponse

profileCollegeman
CIS510discussionpostresponserequirements.docx

CIS 510 discussion post responses.

"Use Case Description versus Activity Diagram"  Please respond to the following:

· Compare a use case description and an activity diagram. Devise a scenario in which you would use a case description, and devise a scenario in which you would use an activity diagram.

· Consider a system needed to store information about computers in a computer lab at a university, such as the features and location of each computer. Ascertain the domain classes that might be included within the domain model. Discuss whether or not you believe an entity-relationship diagram (ERD) would be a suitable model.

SM’s post states the following:Top of Form

A use case description speaks to the client's collaboration with the framework. Whereas, an activity diagram speaks to the arrangement of activities or stream control in a framework like a flowchart. A use case description models the framework and client communications while an activity diagram models the work process of the framework.

On Sunday at 10:00, I prepared a P&J sandwiches for my kids at home. I would be the primary actor using this system. The system contains a bread, peanut-butter, jelly, a bread knife, and a plate. The goal is to create the P&J sandwich for my kids with just the right amount of peanut-butter and jelly.

The activity diagram example below describes the workflow for a word process to create a document through the following steps:

· Open the word processing package.

· Create a file.

· Save the file under a unique name within its directory.

· Type the document.

· If graphics are necessary, open the graphics package, create the graphics, and paste the graphics into the document.

· If a spreadsheet is necessary, open the spreadsheet package, create the spreadsheet, and paste the spreadsheet into the document.

· Save the file.

· Print a hard copy of the document.

· Exit the word processing package.

 

Domain classes are classes that are designed and used for specific domain which can be used by multiple projects that do similar thing. On the other hand, a domain model is a package containing class and activity diagrams. the domain classes that might be contained inside the domain model are the PC's name, model number, and the capacity of every PC

An entity relationship diagram (ERD) is a graphical representation that depicts relationships among people, objects, places, concepts or events within an information technology system. (Margaret Rouse, 2014). I believe that ERD would be a suitable model because it provides a visual starting point for database design that can also be used to help determine information system requirements throughout the computer lab. Nonetheless, while an ERD can be valuable for sorting out information that can be spoken to by a social structure, it can't adequately speak to semi-organized or unstructured information.

 

AH’s post states the following:Top of Form

Compare a use case description and an activity diagram.

Devise a scenario in which you would use a case description and devise a scenario in which you would use an activity diagram.   My devised scenario compelling enough to utilize a case description, real-time estimated times of arrival notifications, this would create an activity diagram of to distinguish, corroborate, and cultivate (Satzinger, 2016) my current cases.  If customers were able to logon to our application and view their estimated time arrival which would lower the call que and increase reservation scheduling.  My activity diagram would be used to describe who will be utilizing the requirements, why and what are the benefits from the additional attributes of functional requirements.

Consider a system needed to store information about computers in a computer lab at a university, such as the features and location of each computer.

Ascertain the domain classes that might be included within the domain model.

The domain classes included within this model would If understood correctly I would have a three case classes, of Features, on one side with  attributes at the bottom and as for the locations, street address, of every computer, which is consisted of the entity-relationship diagram.

Discuss whether or not you believe an entity-relationship diagram (ERD) would be a suitable model.  I strongly believe an ERD is suitable for the model this model is a benchmark for who should be doing what why and what results should be produce, therefore, if there’s anything occurring differently, we have some advantage on downtime.

Reference

Satzinger, J. J. (2016). Domain Model Class Diagram. In J. J. Satzinger, System Analysis and Design (pp. 84-104). Boston: Cengage Learning.

TG’s post states the following:Top of Form

The key difference between use case diagram and activity diagram is that the use case diagram helps to model the system and user interactions while the activity diagram helps to model the workflow of the system.

Use case is an alternative technique for documenting functional requirements for interactive operational systems. It models a dialogue (a process) between a user and a user goal (use case). The technique consists of a diagram and a description. The description of a use case includes pre and post conditions:

· The precondition is the state of the application that is guaranteed to exist in order for the use case to start (no precondition checking within the use case)

· The post-condition is the state of the application that is the result of the success or failure of the use case (state change must be a step within the use case)

Use case diagram and activity diagram are behavioral UML diagrams that describe the dynamic nature of a system. These diagrams provide multiple advantages, it help conceptual modelling and make it simple and easier to understand the system. They help to model business requirements and to get a high-level understanding of the functionality of the system.

ER model is a logical representation of an enterprise data. The main value of carefully constructing an ERD is that it can readily be converted into a database structure. There are three components in ERD:

•Entities: Number of tables you need for your database.

•Attributes: Information such as property, facts you need to describe each table.

•Relationships: How tables are linked together

Base on the given scenario, when storing information about computers in a computer lab at a university, such as the features and location of each computer. EDR poses a few constraints such as:

Loss of information content: Some information be lost or hidden in ER model. Also, it has limited relationship representation; ER model represents limited relationship as compared to another data models like relational model etc. No representation of data manipulation, it is difficult to show data manipulation in ER model. Lastly, it does not allow specification of interactions between the data or model how the data changes (there are no processes in Entity-Relationship).

Reference:

https://www.differencebetween.com/difference-between-use-case-diagram-and-activity-diagram/

https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/2788/Verifying-Use-Cases-Data-Flow-Diagrams-Entity-Relationship-Diagrams-and-State-Diagrams-via-State-Linkages.aspx