Question about SCEA Part2

[Paren Parikh]

Hello Guys,

As part of the SCEA assignment I was planning to create a very high level application context diagram. It shows the external systems and the most important components of the new system to be designed. It also depicts the interaction between various components and systems.

As far as I know this diagarm is not UML compliant . My only intention to have this diagram is to give some more clarity to the examiner.

Should I include this diagram or not ?.

The Assignment deliverables state that "each diagram must be UML compliant"...

Thanks for looking

Paren

[Cameron Wallace McKenzie]

Make sure you are sending them the diagrams they are asking for.

One thing I find is that when people are not confident in their solution, they overcompensate. They have page after page of assumptions, or they put in too many diagrams, or too many notes on their diagrams. The examiners know this too.

The goal is to demonstrate that you can use the standard tools and standard documentation to explain your solution. Are you doing that?

I'm not abject to adding new details, or doing something 'outside' of accepted UML. I doubt my diagrams were all 100% compliant. But if you go overboard, they're going to nail you on it.

Concentrate on what you are being marked on. You don't get extra marks for doing things that are outside of the project.

-Cameron McKenzie

[Paren Parikh]

Hello Cameron,

Thanks for your reply. I am definitely going to include all the diagrams what has been for asked for in the assignment. I am using StarUML for generating Class, Component,Sequence and Deployment Diagrams.

Also I am pretty confident my solution should would be good enough to pass the exam.

But I wished to include the High Level Application Diagram and screen flows same as what I do in my day to day work.. These diagrams are for any
one to get a good understanding of the system being designed.

[Cameron Wallace McKenzie]

Well, I think you've convinced me that it's not a bad idea. Extra detail is always good. It's the superfluous stuff that gets people into trouble.

If everything points to the fact that 'this guy knows what he's talking about' then I think you're golden.

The very best of luck with your submission!

-Cameron McKenzie

[Prashant Purkar]

Hi Paren,

You can draw your high level application context diagram as component diagram and that will make it UML.

I have used a similar application component diagram with some notes to give very high level view of external system and imp components and their relation and your interpretation of the problem..

This was apart from the class etc.. diagrams required for submission.

It helped me mostly to complete my design and can give anyone looking at it an idea what the solution is going to be.

Regards
Prashant