SysML Modeling with Cameo System Modeler

Creating a SysML model in Cameo System modeler.
• Your model is clearly organized and easy to navigate. Your diagrams look nice, and not like a
jumbled mess of lines and nonsense. All blocks/use cases/actors must have Documentation.

• Your model contains at least five blocks, which are named, and which are connected together in
some way. Each block must contain value properties, and at least one block must have inherited
value properties. Each kind of structural relationship covered in lecture must be used at least
once (reference association, composite association, generalization).

• Your model contains at least five use cases and at least three actors. Each use case must have a
scenario using the Cameo use case profile from lecture. Each relationship from lecture
(association, generalization, includes, extend) must be used at least once.

• You must have at least ten requirements in your model. Each requirement shall have a name, ID,
and text. Each relationship from the lecture (containment, refine, copy, derive) must be used at
least once.

• At least one block shall have an IBD under it that demonstrates the use of connectors and
binding connectors. At least one block shall have a parametric diagram that performs some sort of calculation.

• You will have at least one instance of your entire system in the model.

• Each use case in your model must have an activity set as its classifier behavior with each activity being defined in terms of an activity diagram. Across all diagrams you must demonstrate a usage of each type of element demonstrated in the lecture, except for central buffer nodes and data store nodes.

• At least one block must have an activity diagram set as its classifier behavior and this underlying activity must be executable, performing some kind of calculation. Furthermore, at least two other blocks in your model must be tied in to the simulation.

State Machine Diagram
At least one block must have a state machine diagram. Across all potential state machine
diagrams, you must demonstrate a trigger, an effect, an entry behavior, a do behavior, and an exit
behavior.

Sequence Diagram
At least one block must have a sequence diagram as its classifier behavior, and this sequence
diagram must perform some sort of simulation. I need to see at least one type of combined
fragment used on the sequence diagram.

Ports and Flows
Must have examples of interface blocks, proxy ports, and full ports in the model. Must have
examples of flow properties, with flows defined along connectors on an IBD, in the model.

Requirements
At least five requirements must be satisfied and verified by a test case that is defined by some
behavior in the model.

I also started the project, I just need it completed and fixed/error free.

The primary deliverable is a fully functional simulation of our system using SysML. The timeline for this project is one week. Each element should have in-depth detail documented. Use your best judgment for naming conventions and documentation. The system model should focus on the domain of PWR Reactor system. Naming conventions for blocks and diagrams should be based off what is there. Ensure all documentation and naming conventions are moderately detailed but clear. This isn't a big model at all and most of the work has been started, but I just need it completed correctly.