If you can get someone
experienced in DSM, either an external consultant or someone from elsewhere in your
organization, this need only take a couple of days. If it is your ?¬?rst DSM project and
you have no such mentor, a week would be a reasonable time.
The goal of the proof of concept project is to de?¬?ne and implement a small, but
still signi?¬?cant, part of your DSM solution. At the end of the project, you will have a
meeting where you demonstrate the results and bene?¬?ts with a concrete example
to your executives and product developers. The result of the workshop is a partial
modeling and code generation environment for your organization??™s own domainspeci
?¬?c modeling language.
13.3.1 Preparation
Whether you are working on your own or with a mentor, the ?¬?rst phase is to outline the
scope of your DSM solution and gather the materials that form its requirements.
Table 13.2 shows a suggested template for collecting this information. Providing the
answers is a good ?¬?rst task for your DSM creation team, and an effective way of
checking that you have the necessary expertise on the team. If you ?¬?nd yourself having
to ask others for some of the answers, you should consider whether those people or
others with their knowledge should actually be a part of the team.
Set a time for the workshop and arrange a place where your team members can
work uninterrupted by normal business matters.
Pages:
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627