What does it mean to have integrated models? Explain how each of the models relate to the other models – models we have learned are use case diagram, CRUD matrix, class diagram, activity diagram, fully developed use case diagram, system sequence diagram, state machine diagram. How can cross checking between models ensure that the requirements are accurate and correct? What are the dangers of not cross checking between the models?
Reader Interactions
Comments
Leave a Reply
You must be logged in to post a comment.
Iyana Lester says
Each of the UML models relates to one another. The complete set of diagrams work together to define the system requirements and is necessary for us to under the total scope of the “to-be” system. The development of the “next” diagram can also help us correct and revise previous models we created for a true iterative.
A use case diagram identifies all of the use cases of the system. A class diagram identifies the domain classes for the system. CRUD matrix analyzes these two diagrams to ensure they are consistent with each other. Each use case is described either with a fully developed use case diagram or an activity diagram. An activity diagram is used to document the business processes or internal activities for each use case. A system sequence diagram shows the inputs and outputs of each use case. Lastly, the state machine diagram shows possible steps in a use case or identifies the need for a use case. These integrated models work together to specify our requirements and help ensure they are all captured.
Innocent says
Thanks for the explanation. Depending on an analyst’s needs, use case descriptions are usually written at two separate levels of detail: brief description and fully developed description. A brief description can be used for very simple use cases, especially when the system to be developed is small, with a well-understood application.
The fully developed description is the most formal method of documenting a use case, and it includes the following – use case name, scenario, brief description, triggering event, actors, related use case, stakeholders, precondition, post-condition, flow of activities and exception condition ( exception conditions are any condition that causes the system not to follow the expected flow of activities or that leads to abnormal termination of the use case).
Ami Parekh says
I think you do a great job explaining the differences between each UML diagram and how each is connected to one another. Though I agree that creating a “new” diagram can help with the revising of the “old”, I think the “old” can decrease the amount of time it will take to develop the “new” because the actors, attributes, and actions will already be created.
Iyana Lester says
Ami I definitely agree. It is also important to look at the “old” diagrams to sometimes determine that all of the inputs and outputs of the system are captures. Looking at the “old” can help ensure that our inputs and outputs required by the system are all able to be met. This can make the difference between needed to simply update an existing system or finding an entirely new system altogether.
Jing Jiang says
Thanks for the explanation. I learn the difference between UML diagrams more clearly. By cross-checking these different diagrams can ensure the consistency and better meet the design requirements.
Yingyan Wang says
Hi Iyana,
I like your post and thank you for making clear definition of each diagram. And I agree with you that integrated diagram is helpful for specifying requirements and ensuring accuracy.
Mahugnon B. Sohou says
Hi iyana
Thank you for your comment. I think you gave a pretty detailed explanation of the relationship between each types of diagram. I now have a better understanding than before.
Rouying Tang says
Thank you for your explanations, Lyana. You made a good analysis on each diagrams and models and the relationship between them.
Jing Jiang says
Having integrated models means to use multiple modeling techniques together to demonstrate a system to help people to understand the key concepts.
A use case diagram is a picture showing system behavior and the key actors that interact with the system; A fully developed use case diagram describes each use case in detail; A sequence diagram can be used to present sequences for specific use cases; CRUD is an acronym of “creat, read, update and delete”, and CRUD matrix is a table used to display main permissions involve these the operations for each entity within a system; A class diagram shows the static structure of an object-oriented model by using object classes, their internal structure, and the relationships; An activity diagram describes the dynamic aspects of the system which shows the sequence from one activity to another of the system; and a state machine diagram shows different states of an entity and the transitions between those states.
Cross-checking between models can enable a designer to conduct cross-reference and find potential deficiencies in design easier. The consistency and completeness of the design can also be verified in the say. If not cross-checking, it may increase the possibility of the design errors and result in the inconsistency with the requirements, and decrease the efficiency of the subsequent development process.
Innocent says
Great Point, cross-checking between models will help the systems designer or analyst to identify potential deficiencies and correct them as early as possible. Lack of cross-checking may lead to development problems in the business process.
Pascal Allison says
Jing Jiang and tuf50240, great point here.
Now I am of the conviction that cross checking is not an option but a requirement. Failing to cross check is a recipe for delay, increased expenses, loss, etc. Cross check is as important as any other requirement for development process.
Zhixin Wei says
The objective of the SSD is to document the actual input data and the output data that flows between the user actor and the system.
Iyana Lester says
Jing Jiang you make an important point that by not cross checking you could potentially decrease the efficiency of the subsequent development process. The goal of UML is to develop models that protected.from variations in the future. Increasing the efficiency during development can help separate those parts of the system that are likely to change from those that are not.
Yingyan Wang says
I agree with you, Jing. Cross checking is important since without it, we may not be able to find errors or ignore potential risk easier, which may lower performance and efficiency.
Mahugnon B. Sohou says
You made a very good Point. Cross-checking helps identify and fix inconsistencies. Not using cross checking could reduce the efficiency of the development process. Thank you for emphasizing the importance of using it
Rouying Tang says
Hello Jing, good job.
Thank you for your explanations toward the case diagram, CRUD, class diagram, activity diagram and the importance of cross-checking between models.
Qiyu Chen says
good point. The sequence diagram can be used to present a sequence for a specific use case; CRUD is an abbreviation for “create, read, update, and delete”, and the CRUD matrix is a table for displaying the main authority, which relates to the operation of each entity in the system;
Innocent says
The word integrated means – uniting things that can stand alone usefully but that are even put together, and ‘modeling system’ has to do with the computer software that supports the modeling life-cycle. Use case related models are the “fully developed use case description,”. UML activity diagrams, UML systems sequence diagrams.
The Fully Developed Use Case descriptions – are used to document the context, purpose, description, conditions, and workflow of each use case.
Activity diagrams can be described as a graphical depiction of the use case workflow and are useful in illustrating the alternative paths through a business process. And the Systems Sequence Diagrams are used to document the inputs and outputs which are passed between the user and the system during a use case. These models help to document the internal steps of a Use Case and developing these models force the analyst to ask meaningful questions that help improve the understanding of the requirements. The State Machine Diagram, can be described as a class related model. It is important for us to note that – for some object classes in the domain model, it is necessary to understand the life cycle of individual objects. A state machine diagram documents what these status conditions are and how an object changes status condition by transitioning from one state to another.
Cross-checking between models will help the systems analyst to identify anomalies, discover potential errors and ensure that the requirements are accurate and correct.
Example – To have a truly integrated supply chain, information must be passed between companies. The object-oriented models provide a strong basis to document interface requirements. And the Object-Oriented system development provides the techniques to pass data between companies. The dangers of not cross-checking between models are that the analyst may not be able to fully comprehend the sequence of steps to complete a business process. It will be difficult to understand the different flows of activities ( activities are called scenarios or use case instances). Most importantly, not cross-checking between models may lead to a poor description of the scenario, triggering events and undesirable results or outcome.
Zhixin Wei says
Use case diagrams are used to specify:
(external) requirements, required usages of a system under design or analysis (subject) – to capture what the system is supposed to do; the functionality offered by a subject – what the system can do
Hanqing Zhou says
Thank you for your sharing. I like what you mentioned about the different functions for the different types of the diagram and you use example to explain the cross checking. Because a simple or we can say the one diagram can not express the whole processes, thus, the cross checking is a method to make sure the steps are match with other diagram.
Mahugnon B. Sohou says
Thank you for your post. You made a really good point describing each diagram and their functions. it definitely helped helped me to have a better understanding. Because on diagram may not be enought to express the entire process, we therefore need cross checking to make sure all the diagrams match.
Xiaozhou Yu says
The example you provided is well described, and gave us a clear view of the benefits of using different model and cross checking.
Pascal Allison says
Integrated model refers to the usage of models to cover a system events, description, organization, and operation. The relationship is such that one model is used to correct and or revise the other for success. All model put together to achieve a specific goal.
User case diagram shows the user interaction with the system which reveals the relationship between the user, the system, and other user case if any.
The acronym CRUD stands for Create, Read, Update, or Delate. CRUD matrix identifies or structures tables in a system. The table are developed from the class diagram.
The class diagram is like the building block of a system. It describes the structure of a system by listing classes, attributes, and the relationships among objects. This derived from the use cases
Activity diagram is a flowchart that represents the flow of activities. It shows all actions between cases. The list is from one activity to another activity.
The fully developed use case diagram is the diagram that documents all use cases. It is known as most recognized technique for documenting a use case.
A system sequence diagram (SSD) is a categorization diagram that shows, for a specific situation of a use case, the actions, or effects that external actors create, order, and other
effects actions with other system. It expands the view of the use case.
State machine diagram is a behavior diagram which shows distinct behavior each part of the system through events. State machine diagrams can also be used to express the usage decorum of part of a system.
Cross checking between model can ensure that the requirements are accurate and correct by constraining the meaning of the diagrams, relating each model against other models in relationship to the description system. If the models are not cross checked, there could be lapses: failed analysis, inconsistencies, incompleteness, etc.
Innocent says
Perfect!
Cross-checking between models will help the analyst to ensure that all requirements are accurate and/or in-line with the set objectives. Unidentified deficiencies or error might cost the business a lot – in terms of output, financial or material damage(s) and many more.
Zhixin Wei says
In UML terms, subject is a classifier playing the “subject” role. They did not create a separate special class for subject, as it was done with actor and use case. UML 2.5 states that a subject of a UseCase could be a system or any other element that may have behavior, such as a Component or Class
Mengqiao Liu says
Thank you for your explanation of integrated model and other diagrams. Your explanation is very clear.
Mahugnon B. Sohou says
Hi Pascal
Cross-checking help the analyst to make sure all the requirements are aligned with the business objectives. Also like mentioned in a previous comment earlier, any unidentified error could be highly costly to the business.
Xiaozhou Yu says
The explanation of each model is well described, So it is clear, they have different functionality, and should be use as combination for better system process representation.
Zhixin Wei says
There are many well-formedness rules of each UML element in UML specification, but there are not any rules that check the consistency among UML diagrams.The cross checking between models ensure that the requirements are accurate and correct. we propose several checking rules to improve the consistency among UML diagrams, especially between UML static diagram and dynamic diagram. So we make explicit some requirements on consistency of UML diagrams that are buried in the original well-formedness rules of UML specification and derive some checking rules.
Karabo Ntokwane says
You are right, cross-checking is important as it allows for early detection of discrepancies between the different models and gives the designers a chance to make corrections before the system development stage. Like you said, it also helps to identify any inconsistencies for examples the same entities should appear in the diagrams, showing similar processes and data stores. Cross checking also checks for continuity as the model mature.
Iyana Lester says
You bring up an important point that while we have many rules for the syntax and design of models it is important to develop this same “attention to detail” in the cross checking rules of various models. I think as auditors, when cross checking diagrams, it is important for us to also evaluate how significant an error found is. For example, is it as simple as the diagram being inconsistent with the UML specification/standards you mentioned. Or more severe where cross checking the models shows that they are self-contradictory to the system’s or software’s key requirements.
Yingyan Wang says
I agree with your idea. Cross-checking is a good tool to ensure the accuracy and completeness.
Rouying Tang says
Oh, Zhixin little sister, like your post the most. They are so cohesive and easy to read. I agree with you on the idea that the cross checking between models ensure the accuracy and the correctness of the requirements.
Ami Parekh says
I think you bring up a good point about cross checking and how doing so will help with finding discrepancies within UML diagrams. Putting this idea into practice will help solidify the diagrams and make sure all users are on the same page.
James Jeffrey Scheuren says
Consistency is key in these diagrams, I agree. You need everything to “talk” to each other and the language needs to be consistent in order to guarantee success.
Karabo Ntokwane says
When designing a system, requirements are gathered, and these requirements are represented using different models. To have integrated models means these models are used together to show the process, logic and timing, and data of the system components. The use of integrated models enhances the system making it more efficient, reduces gaps ensuring the delivery of a quality system that meets the user requirements.
The use case is used to show the system’s functionality. They are used to develop activity diagrams and system sequence diagrams.
An activity diagram is used to show shows the conditional logic and the flow of system activities.
The class diagrams show the relationships between the different entities in a system. The sequence diagram is used to come up with the different classes.
State machine diagrams show the class methods or behavior.
CRUD matrix shows the different authorizations in the system of creating, reading, updating and deleting, this is based on the use case diagram.
Basically, use case diagrams and activity diagrams are functional models showing the use of the system, the CRC cards and class diagrams on the other hand show the structure of the system, lastly the sequence diagrams, CRUD matrix and state machines are behavioral models.
Cross checking ensures efficiency by confirming that nothing has been omitted, and that the models are correct as expressed by the users when giving the requirements. Cross checking also ensures that the structure, behaviors, relationships remain the same throughout the different models.
Iyana Lester says
You made some great points regarding the benefits of integrated models and the overall purpose of the models. As auditors we need to understand the functional (i.e. use case and activity diagrams), structural (i.e. CRC cards and class diagrams), and behavioral (i.e. CRUD and stat machines) aspects of a system in order to be able to asses the internal controls and risks of an organization’s information technology structure, operations, and/or software programs.
Lezlie Jiles says
HI Karabo,
I agree with your CRUD statement. The CRUD matrix is driven by the use case diagram which assist in identifying and driving the user’s authorization.
Binju Gaire says
I agree with your explanation, Karabo. Integrated models refer to using different models to showcase the processes of the system. Using only one model may not be effective in understanding the logic and timing of the system. A combination of a few models such as use case diagram, activity diagram and so is helpful in interpreting the system. I also agree that cross checking is an important process to maintain consistency between different models.
Yijiang Li says
In a real business world, each business process is different and complicated. Therefore, a single diagram model is not enough to illustrate the complete business case, so we have to apply integrated models. By utilizing cross-checking between models, we can easily realize any missing factor which has been defined by the narrative within a single diagram. If so, we can just apply another type of diagram to fix this issue. Without performing a cross-checking between models, we are not able to figure out a potential error in the design and planning phase unless the real issue actually happens in our business activities. It could greatly affect our operating efficiency and cause a potential economic loss.
Jing Jiang says
Well said, Yijiang.
Using integrated diagrams is necessary when designing a system. It will help a reader better understand the main concepts, reduce potential inconsistency between diagrams and find potential deficiencies in time. I totally agree with you that finding errors earlier design phase is important to reduce perhaps financial losses and operational inefficiencies.
Jing Jiang says
Smart as you:)
Mahugnon B. Sohou says
I agree with you. Multiple methods should be used to make sure the entire business process is fully described. All your points regarding each model are brief but describes pretty well what each model does and what it’s used for.
Linlan Chen says
You are so smart!
Karabo Ntokwane says
You are right cross checking allows designers to check for consistency among the different models and correct if anything was left out. Continual cross-checking, guarantees well designed structure and system models. For example, a use case provides input and methods/behavior of the system and these are represented in a class diagram. That is the reason why we need integrated models.
Hanqing Zhou says
Thank you for your sharing, Yijiang. because the components of the integrated models have different functions, so we need to combine all of them to describe the whole business.
Yingyan Wang says
Hi Yijiang,
I agree. Integrated models are good tool to provide more functions when the business case is complicated. And I also agree with Linlan, you are so smart!
Hanqing Zhou says
Thank you for you sharing. The cross checking help the designer find the potential issues which can help the organization to reduce cost about also reduce the time cost, which increase the work efficiency. Same with LInlan and Yingyan, you are very smart!
Mengqiao Liu says
Hi Yijing,
I am so happy that lots of our classmate agree with you and so do I! So smart you are!
Xinteng Chen says
I agree with you, because people should use multiple methods to make sure fully description of business process. The function is limited on a diagram. Each model or diagram should play specific role in communication and description. Therefore, I like your post. I strongly agree with that you are smart.
Vittorio Christian DiPentino says
Yijiang,
You are completely right. A business is complex and requires many diagrams in order to fully represent the case and understand if something is missing. It takes someone who is really smart, someone
like you, to understand this. Thank you for sharing with us.
Yijiang Li says
Thanks, Vito. I was so surprised you also played this naive game with them. Haha.
Rouying Tang says
Hello Yinjiang, thank you for your sharing. As you stated single diagram model is not enough to illustrate the complete business case. And agree with anyone else, you are so smart!
Ami Parekh says
I think you make a solid point defining that all business practices are different therefore require multiple diagrams to make sure they are depicted correctly.
Mahugnon B. Sohou says
Different models are used to represent the different requirement gathered in a system design. To have Integrated models means the use of models together to cover a process. Using integrated models ensures the system’s effectiveness to that meets requirements, because the models revise each other to deliver a quality system.
The use case diagram is used to show the user interaction and the system’s functionality. They are used to show the relationship between the user and the system.
An activity diagram shows the flow of activities in a system and all conditional logic between cases
The class diagrams comes from the use case and shows the structure of a system using classes, attributes, and the relationships between them in a system.
State machine diagram shows how different parts of the system behave as well as their class method.
CRUD stands for Create, Read, Update, or delete. It shows the different authorizations in the system and is developed from the use case diagram.
A system sequence diagram (SSD) is a diagram that show the effect of external actors for a specific situation of a use case. Allows for an extended view of the use case
The class diagrams show the structure of the system, while the activity diagrams and use case diagrams show the use of the system. The CRUD matrix, state machines and sequence diagrams are more of a behavioral models.
Cross checking between models ensures efficiency by confirming that all the requirements are correct and accurate. It also ensures that the structure, and relationships remain the same throughout the different models. If the models are not cross checked there could be inconsistencies.
Iyana Lester says
Mahugnon you mention an important point that we must make sure the relationships remain the same throughout the different models. This can be a red flag if we notice differences in how the “actors” and “objects” interact with one another as we move into different models.
Hanqing Zhou says
Thank you for your sharing, Mahugnon. One thing you mentioned about is the efficiency. You are right, the cross checking can help designers to find the issues in the early stage which reduce the time cost of the whole project.
Lezlie Jiles says
HI Hanqing,
I agree. Cross checking will not only reduce the time and cost but will also ensure that the project is successfully completed and meet all requirements.
Haitao Huang says
UML, stands for Unified Modeling Language, is a modeling language consisting of an integrated set of diagrams that are used to assist system and application developers for designing, visualizing, and documenting the requirements of software, business process, and systems. UML consists of a set of diagrams and each diagram focus on different aspect of the system, and each of diagram represents different level of detail. For example, a class diagram describes types of objects in the system and various kinds of static relationships between them. An activity diagram is a flowchart that represents the flow from one activity to another activity. There is no single diagram that is capable of representing all aspects and detail of a system, therefore, cross-checking between models ensure that a system development process captures all necessary requirements of the system.
Xinteng Chen says
I agree with you, because each diagram has different functions. It is important for an organization to use multiple types of models and diagrams. It helps the organization describe its business process, and check for mistakes.
Yijiang Li says
You made a good explanation of United Modeling Language (UML), Haitao. Under the UML, there are a variety of diagrams and each of them serves different business processes. As you mentioned, none of a single diagram can satisfy all the business processes at the same time. Therefore, an enterprise has to utilize cross-checking between models to make sure all facts of the narrative and requirements have been integrated into its diagrams.
James Jeffrey Scheuren says
I see that there is no all-encompassing diagram that will absolutely run a system. I agree that cross-checking is key and having multiple diagrams is important.
Dongjie Wang says
Thank you for your sharing, Haitao.
None of a single diagram can represent all the useful information. Therefore, organizations should use cross checking method to ensure the accuracy and completeness.
Ami Parekh says
I like how you mention that different models exist for different reasons so its important to use all of them as a reference and also to make sure everything you’re doing on other diagrams makes sense.
Hanqing Zhou says
When the organization start designing the system, there are many information are required to be collected. However, the relations and processes among these information are complex. Thus, we need to use different models to represent the information we want. The integrated models are used to show the processes which contained steps and data.
The use case is used to express the system functions like system behaviors and how the actors in the processes.
The activity diagram is used to show the flow of the system activities.
The class diagram gives the relationships among the entities, and the sequence diagram show the relationship between the classes.
CURD means ” Create, read, update and delete” and the CRUD matrix mentions about the different authorizations in the system “Create, read, update and delete.”
Cross-checking can help designer to figure out the potential issues in the early design stage. If we do not use the Cross-checking, it may cause the steps from each diagrams do not match with each others.
Xinteng Chen says
I agree with you, because cross checking helps people find out problems by using different methods. If people use only one method, it is hard to find the problems.
Yingyan Wang says
I agree with your idea. Integrated models help solve complicated information and cross checking is a good way to help us find errors.
Mengqiao Liu says
Hi Hanqing,
I agree with you for cross-checking can help the designer to figure out the potential issues because they focus on every diagram they design, so they can find out the problem, logical error, or defect easily and quickly than other people who are not envolve in the designing.
Mengqiao Liu says
involved*
Linlan Chen says
Thank you Hanqing! I like your comment that CRUD means ‘Create, Read, Update or Delete’, and the CRUD Matrix identifies the Tables involved in any CRUD operation.
Rouying Tang says
Hello Hanqing,
You made a good analysis toward the question why cross model analysis is necessary. I agree with you on your idea that the complexity of the information and the large amount of data volume urgent it to happen.
Thank you for your sharing.
Xiaomin Dong says
I agree with you, a CRUD diagram shows what types of processing is performed on data by a system, indicating them in a matrix format for each function.
Xinteng Chen says
Different diagrams have different functions to describe the business processes. If an organization only uses one kind of diagram, it will not fully display the whole process of business activities. For example, data flow diagram is used to describe how the data go though in the business process. ER diagram is used to understand the relationship between different entities. Integrated model means an organization uses enough method for its business process. Lack of integrated model may cause misunderstand and miscommunication, because people could not fully understand the business process, so they may have problems in cooperation. Cross checking is important because it helps people think about a question based on different perspectives. If people only use one model or diagram, the problem on the diagram may not be found.
Linlan Chen says
Thank you Xinteng! I agree with you lack of integrated model may cause misunderstand and miscommunication because people did not understand the whole business process.
Lezlie Jiles says
HI Xinteng,
Great post. Also, when cross checking in not completed it could cause the project to fail because of the continued errors that may occur and the time/money needed to resolve them. If cross checking is preformed it will assist in eliminating these issues.
James Jeffrey Scheuren says
I think the point about only having one diagram makes a lot of sense. If you only have one diagram to work off of, there could be some confusion to come out of it.
Xiaomin Dong says
Well said. In my opinion, in order to cross checking, simulation is an useful method to explore or identify the concerned behaviors or performances of real systems.
Qiyu Chen says
I agree with you. Different charts have different functions to describe business processes. If an organization uses only one kind of chart, it will not be able to fully show the entire process of business activities
Mengqiao Liu says
Integrated models help corporations, executives, shareholders, employees and clients to understand the structure of the companies deeply and clearly. Each of the models presents one structure in different focuses. Each diagram suitable for the different group. Some of them are suitable for employees to learn, understand and training; some of them are suitable for executives to analyze, adjust and make decisions, and so on. Each diagram has effect with other diagrams, because they may have the same object, class, or attribute, and people put them in different flow charts to present the diagrams they want other people to understand. During the processing of making these diagrams, people can find the relationship between these objects and different diagrams, which double-check the correctness of these models. That is why cross-checking between models ensure the requirements are accurate and correct. If they do not, each diagram may exist defect or logical error.
Linlan Chen says
Yes, Mengqiao, Also, The CRUD Matrix is an excellent technique to identify the Tables in a Database which are used in any User interaction with a Web Site.
James Jeffrey Scheuren says
I definitely agree that without using cross-checking there is a good chance of defects and logical errors. One needs to make sure that everything is working together and working well.
Xiaomin Dong says
Well said. With cross checking between models, it can ensure that the requirements are accurate and correct.
Qiyu Chen says
good point. Each figure fits into a different group. Some of them are suitable for employees to learn, understand and train; some of them are suitable for managers to analyze, adjust and make decisions, etc.
Yingyan Wang says
Integrated models are good to use when facing complicated information. Not like a single diagram, which only can handle limited information, integrated models help an organization to figure out right thing when business case or process is complicated. In integrated models, use case diagram shows system behavior, along with key actors that interact with system. Class diagram using UML drawing tools and is the object-oriented data modeling notation. Activity diagram shows the conditional logic for the sequence of system activities needed to accomplish a business process. Besides, cross checking between models will ensure the requirements are accurate and correct because it can help find errors. Without cross checking between the models, we may miss some mistakes inside models which may result time wasting and increase financial cost.
Linlan Chen says
Hello Yingyan, I agree with you that missing cross checking between the models may cause some mistakes inside models which result in business processing time wasting and increase the fund
Yijiang Li says
That’s true, Yingyan. A single diagram can only process limited information, however, most business cases are complicated and involved in different type of entities and associations. Utilization of integrated models can easily overcome the difficulties that a single diagram encounters through building a connection among different kinds of the diagrams and extracting the necessary components based on narrative and business requirements.
James Jeffrey Scheuren says
Cross-checking is definitely an essential part when developing any system. I definitely agree that it helps find errors when there are so many diagrams to follow.
Dongjie Wang says
Good Point Yingyan,
The single diagram can only contain limited information, but an integrated model can include different information. The integrated model can ensure the consistency among all the diagrams, which can improve the development quality and speed.
Xiaomin Dong says
Nice point. Each model/diagram have different function, integrated models means combine the multiple models/diagrams together to interpret a system.
Ami Parekh says
I agree with your statement that integrated models can help when organizing a lot of information that are within the models. I think you also bring up a good point about how cross-checking and help catch a mistake of a model and save time and resources down the line.
Qiyu Chen says
Thank you for sharing. using case diagrams show system behavior and key roles in interacting with the system In the integrated model.
Linlan Chen says
Integrated model is a way to measure the flexibility and time frame of developing new products based on combination of all of the activities that go into such production rather than measuring each activity separately.A CRUD matrix is a table showing the Functions in an application containing SQL statement affecting parts of a database.It is very valuable to combine a CRUD Matrix with the analysis of possible User Scenarios for the Web Site.
Cross training is very helpful for us to check (something, such as data or reports) from various angles or sources to determine validity or accuracy. If we don’t use this between models may cause the potential issues we can’t find.
Dongjie Wang says
Thank you Linlan, I agree with you. Without checking, the organization could omit some mistake in the diagrams.
Xiaomin Dong says
I agree with you that it is important to having cross checking. It may find some mistakes that we couldn’t find without cross checking.
Qiyu Chen says
I like your point. The CRUD matrix is a table that shows the functions in an application that contains SQL statements that affect various parts of the database. Combining a CRUD matrix with the analysis of possible user scenarios for a Web site is very valuable.
Lezlie Jiles says
How can cross checking between models ensure that the requirements are accurate and correct?
Cross checking ensure consistency and completeness between the diagrams, which will result in a quality product. Cross checking between models guarantees that the stated requirements are correct and the information is valid in different diagrams.
What are the dangers of not cross checking between the models?
If cross checking is not completed the project will be placed in jeopardy of having many errors thereby effecting the product’s outcome. Not cross checking would also drive the cost of the project up because time and effort would be consumed with correcting the system’s issues. Once the main elements of use case and categories of data have been identified it is useful to develop a matrix, cross-referencing these to each other and showing the specific interaction between that this matrix is often referred to as a crud matrix.
Lezlie Jiles says
What does it mean to have integrated models?
An integrated model is the assessment of several models which combines their activity into a single agenda opposed to measuring each model separately. Thereby identifying inconsistencies, and controlling the accuracy of the information.
Lezlie Jiles says
Explain how each of the models relate to the other models – models we have learned are use case diagram, CRUD matrix, class diagram, activity diagram, fully developed use case diagram, system sequence diagram, state machine diagram.
Use case diagram assist in capturing the functional requirements of a system. It is a picture that depicts the system’s behavior and the interacting key actors. Whereas, a class diagram depicts the stationary structure of an object oriented model, the object classes, their internal structure. As well as the relationship in which they participate. The CRUD matrix examine tables in a database that are utilized in any user interaction to ensure that they are reliable. An activity diagram provides the restricted logic in order of the system activity necessary to achieve projected business process. Activity diagrams could also be used as the phases in a use case diagram. A fully developed use case descriptions are used to document the contacts, purpose, description, conditions, and workflow of each use case and SSD document the inputs and outputs that are passed between the system and user throughout the use case. These models document the internal stages of a use case, and develops an analysis to enhance detailed questions, which in turn deepens the understanding of the stated requirements.
Ping Sun says
Integrated assessment modelling (IAM) or integrated modelling (IM)[a] is a type of scientific modelling often used by the environmental sciences and environmental policy analysis. The modelling is integrated because environmental problems do not respect the borders between academic disciplines. Integrated assessment models therefore integrate knowledge from two or more domains into a single framework. Integrated modelling is referred to as assessment because the activity aims to generate useful information for policy making, rather than to advance knowledge for knowledge’s sake. Integrated assessment modelling is that part of integrated assessment that relies on the use of numerical models.
Integrated assessment modelling has a long history, and scholars disagree on the first precedent. However, it became recognizable as a sub- or inter-discipline in the late 1980s with a focus on understanding and regulating acidification. Integrated assessment modelling was further developed in the area of climate change, inter alias in the context of the Energy Modeling Forum.
Rouying Tang says
Integrated models content completed factors and logical relations. Cross checking between models ensure that the requirements are accurate and correct through comparing the processes of relating different models and checking the information missing and logic consistence. In addition, different departments may be directed by different diagram, the whole project may not be aligned to each part, without this steps,
The use case diagram presents the interactions between the users and the system and the use cases in which users is involved. The CRUD matrix (Create, Read, Update or Delete) is used for identified the tables involving all sections, relationships, related elements to analysis the possible user scenarios for the web site. Class diagram is a type of static structure diagram describes the structure of a system with its classes, attributes, methods and the relationships, while the activity diagram is used for stating the dynamic aspects of the system by showing the flow between activities. “State machine diagram describes behavior of a part of designed system through finite state transitions.”
James Jeffrey Scheuren says
Having integrated models means having a connected experience of different diagrams that all contribute to the ultimate system that is being created. A use case diagram is a simple representation of what users are doing in a certain system. CRUD matrix helps create the tables in a database, as it represents the what to create, read, update or delete. class diagram show a system’s classes, attributes, operations, and the relationships of objects, activity diagram describes the flow of one activity to the next, fully developed use case diagram is a very developed explanation of the processes in a system, system sequence diagram explains when events are supposed to occur in a system, state machine diagram essentially explains computation in a system. These are all connected because they all support the function of a system.
Cross-checking models can ensure accuracy because you can get a glimpse into how all of the diagrams work together. The steps need to correspond with each other for everything to run efficiently. Not doing this could lead to difficulties in system success and being able to pinpoint the actual problem.
Xiaomin Dong says
I believe that have integrated models means combine the multiple models/diagrams together to interpret a system. Each model/diagram have different function. For example, use case diagram is a representation of a user’s interaction with the system that shows the relationship between the user and the different use cases in which the user is involved; a CRUD diagram shows what types of processing is performed on data by a system, indicating them in a matrix format for each function; a class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system’s classes, their attributes, operations (or methods), and the relationships among objects; activity diagram is another important diagram in UML to describe the dynamic aspects of the system. Activity diagram is basically a flowchart to represent the flow from one activity to another activity. The activity can be described as an operation of the system. The control flow is drawn from one operation to another, so and so forth.
In order to cross checking between models to ensure that the requirements are accurate and correct, we can do the simulation. Simulation is used to explore or identify the concerned behaviors or performances of real systems.
Binju Gaire says
Thanks for the thorough explanation Xiaomin. You make a very good about simulation it terms of cross checking. I guess cross checking is significant not only to ensure that there are no gaps between the models, but also to run a simulation which can give a very good idea on how the system can be interpreted after completion.
Xiaozhou Yu says
There are various way to express a process, different type of models have different characters and capability. The detail they can represent can be limited, Using different model to describe the process and cross checking can make sure the details are represented as much as possible. Also, functionality of different models are different and limited, some part of process may be applied to certain types of model, but it doesn’t mean the whole process can be descried decently using one model. It is important to understand the application of different types of model and use them for the concise representation and meet requirements accurately.
Binju Gaire says
Well said, Xiazhou! Having an integrated model not only means combining different models to interpret a system, but also fully realizing the benefits of cross checking to ensure thorough representation.
Chenhui Lai says
Integrated requirements model way to measure the flexibility and time frame of developing new products based on a combination of all of the activities that go into such production rather than measuring each activity separately. Once the main elements of use cases and categories of data have been identified, it is useful to develop a matrix, cross referencing these to each other and showing the specific interactions between them. This matrix is often referred to as a CRUD matrix. A CRUD matrix is developed by listing the classes from the class diagram (or the entities if entity relationship modelling is being used) along the side of the matrix. Completing the relevant intersections between use cases and classes with a combination of C(reate), R(ead), U(pdate) and D(elete), depending on whether the use case needs to create, read, update or delete one or more instances of the class. An activity diagram visually presents a series of actions or flow of control in a system similar to a flowchart or a data flow diagram. Activity diagrams are often used in business process modeling. They can also describe the steps in a use case diagram. Activities modeled can be sequential and concurrent. In both cases an activity diagram will have a beginning and an end. Use case related models are the “fully developed use case description,” UML activity diagrams, and UML system sequence diagrams (SSD). The “fully developed use case descriptions” are used to document the context, purpose, description, conditions, and workflow of each use case. Activity diagrams are a graphical depiction of the use case workflow and are useful in illustrating the alternative paths through a business process. SSDs are used to document the inputs and outputs that are passed between the user and the system during a use case. Not only do these models document the internal steps of a use case, but the very act of developing these models force the analyst to ask detailed questions and help improve the understanding of the requirements. The wholeness or fullness of documenting requirement engineering models like use case model, result in a better quality software product. Thus, cross checking between models ensure that the requirements are accurate and correct since the rquirements left uncovered in one model can be seen through other model. If we miss anything or commit any mistake in the models, it may transmit to analysis phase. Further there are chances that the same bug is propagated to design, testing and so on until deployment. The cost of eradicating bugs in testing is very pricier than that of its removal in the starting phases or models. It is therefore very necessary to cross check between the models we are developing and after the model making process is verified it is necessary to validate the models; that is to declare that the models we have made are correct.
Dongjie Wang says
An integrated model provides the connection between different diagrams which can help organizations clarify the stakeholders’ needs, development requirements and business rules. Different from a single diagram, an integrated model contains various diagrams which represent diverse information. The use case diagram shows the system boundary, the interaction between key actors and the system, and the main behavior would happen within the system. The Entity Relationship and class diagram notations explain the characteristics and structure of data independent of how the data may be stored in computer memory. CURD matrix analyzes the diagrams and makes sure all the diagrams are consistent. The cross-checking can help the designer to find the inconsistency between different diagrams. The inconsistency could cause system errors, fail the requirements, and incompetent.
Binju Gaire says
To have an integrated models means to apply a combination of multiple modeling techniques to interpret a system. The models we have learned, each relates to one another. For instance, the elements of use case diagrams are used in developing matrix which are often referred to CRUD matrix. Similarly, the CRUD matrix is developed by listing down the classes from class diagram. When it comes to activity diagram, they can be used in describing the steps in a use case diagram. Overall, these models help in understanding how activities interact with each other to create a system.
Cross checking between models is quite significant as it ensure that the requirements are accurate and correct by finding any existing inconsistencies between the models. Not cross checking can lead to making mistake and not fulfilling the requirements.
Jason M Mays says
The business needs to have multiple stakeholders is reflected in the use of different models. In both cases there are different perspectives that are considered to understand how to get from point A to point B. Use cases help visualize who uses the process. Some one from marketing or a BU manager may be the one to explain who would be a use case. The dataflow that a user user generates through interaction may be explained by IT. In order to understand the connection on a broader level you can look at an activity diagram. The different models should be looked at as the smaller parts of an integrated visualization of the process
Vittorio Christian DiPentino says
Business processes can be complex and detailed to the point that a single diagram model will not suffice in illustrating the business case. That is why integrated models are needed. By cross-checking models, it is possible to find missing factors that where been defined by the narrative. Applying another type of diagram can fix this issue. Potential error in the design and planning phase may not be found without cross-checking between models and the real issue may be found during business activities. If this were to happen, it could affect operating efficiency and cause a loss.
Qiyu Chen says
Each map has a different function. For example, the use case diagram is a representation of the user interacting with the system. The system displays the relationship between the user and the different use cases involved by the user; a CRUD diagram shows the type of processing a system performs on the data and represents each function in a matrix format. A class diagram in the Unified Modeling Language (UML) is a static structure diagram that describes the structure of the system by showing the system’s classes, their properties, operations (or methods), and the relationships between the objects; the activity diagram is Another important figure in UML is used to describe the dynamic aspects of the system. The activity diagram is basically a flowchart that represents the flow from one activity to another. This activity can be described as the operation of the system. Control flow is from one operation to another, and so on.
In order to cross-check between models to ensure that the requirements are accurate and correct, we can simulate. Simulations are used to explore or identify the relevant behavior or performance of a real system.