Challenge    I choose Visualization tool, as describe in module 1 of this course, to help us as software  development solution provider for government agencies in Malaysia to correctly define  scope of work and get high-level view of list of functions (software features) needed from  our clients. In any software development project, we use Visualization tool a lot especially  during initial scope of work meeting, requirements analysis and software design phase.  Correctly defined scope of work and software functionalities early in the project timeline  will avoid misunderstanding and miscommunication between stakeholders. Visualization  tool widely adopt by software engineering communities to build high-quality software  solution within timeline and budget.    Selection    I am using Use Case diagram as Visualization tool in early requirement analysis and scope of  work meeting in every software development projects. Use case diagram consist of straw  man as users (or actor) and eclipse-shape figures as functionalities required in the system.   Example of Use Case diagram is shown below:

Use case diagrams help solution architect, system analysts and software designers to  capture all user requirements and to define scope of work early in software development  project. Use case diagram will be referred in future meeting between clients and software  development teams for any improvement or enhancement as the development work  progress.       Application    To create Use Case diagram, we usually use software tool such as Visual Paradigm  (Community Edition) to draw and keep track of version of the diagram. Initial diagram  usually created by Software Engineer base on initial collective understanding of software

Figure 1 Example of Use Case diagram

development team. A few straw men figure (as user of the system); and a few eclipse-shape  figure (as function or feature) is added to the diagram. Users and functions are connected  via straight line to indicated their relationship. This initial diagram will be sent to client via  email for their perusal. Next, the diagram will be use in initial scope of work meeting and  user requirements workshop. The Use Case diagram will aid mutual understanding between  client and software development team.     Insight    By preparing Use Case diagram beforehand and then explain the diagram to clients during  initial scope of work meeting and during requirements gathering phase helps to avoid  misunderstanding and act as a catalyst for discussion between stakeholders. Any missing  information can easily be added to the diagram; and any wrong information can be either  edited or removed from the diagram. This collaborative work between clients and software  development team increase mutual understanding about tasks in hand and also increase  trust between stakeholders. The updated version of Visualization tool diagram shall be  shared among team members and frequently referred as development work progress. Use  case diagram is easy to use and easy to understand.        Approach    With many positive feedback and valuable time saving of using Visualization tool, I would  continue using this tool in the future. I discovered that Visualization tool help us a lot in  capturing the correct user requirements, understand scope of work and achieve higher  mutual understanding between clients and software development solution provider.  Visualization tool diagram (such as Use Case diagram) can be used as main reference for  discussion between the stakeholders of any software development project.


Challenge I choose Visualization tool , as describe in module 1 of this course , to help us as software development solution provider for government agencies in Malaysia to correctly define scope of work and get high - level view of list of functions ( software features ) needed from our clients . In any software development project , we use Visualization tool a lot especially during initial scope of work meeting , requirements analysis and software design phase . Correctly defined scope of work and software functionalities early in the project timeline will avoid misunderstanding and miscommunication between stakeholders . Visualization tool widely adopt by software engineering communities to build high - quality software solution within timeline and budget . Selection I am using Use Case diagram as Visualization tool in early requirement analysis and scope of work meeting in every software development projects . Use case diagram consist of straw man as users ( or actor ) and eclipse - shape figures as functionalities required in the system . Example of Use Case diagram is shown below : Use case diagrams help solution architect , system analysts and software designers to capture all user requirements and to define scope of work early in software development project . Use case diagram will be referred in future meeting between clients and software development teams for any improvement or enhancement as the development work progress . Application To create Use Case diagram , we usually use software tool such as Visual Paradigm ( Community Edition ) to draw and keep track of version of the diagram . Initial diagram usually created by Software Engineer base on initial collective understanding of software Figure 1 Example of Use Case diagram development team . A few straw men figure ( as user of the system ) ; and a few eclipse - shape figure ( as function or feature ) is added to the diagram . Users and functions are connected via straight line to indicated their relationship . This initial diagram will be sent to client via email for their perusal . Next , the diagram will be use in initial scope of work meeting and user requirements workshop . The Use Case diagram will aid mutual understanding between client and software development team . Insight By preparing Use Case diagram beforehand and then explain the diagram to clients during initial scope of work meeting and during requirements gathering phase helps to avoid misunderstanding and act as a catalyst for discussion between stakeholders . Any missing information can easily be added to the diagram ; and any wrong information can be either edited or removed from the diagram . This collaborative work between clients and software development team increase mutual understanding about tasks in hand and also increase trust between stakeholders . The updated version of Visualization tool diagram shall be shared among team members and frequently referred as development work progress . Use case diagram is easy to use and easy to understand . Approach With many positive feedback and valuable time saving of using Visualization tool , I would continue using this tool in the future . I discovered that Visualization tool help us a lot in capturing the correct user requirements , understand scope of work and achieve higher mutual understanding between clients and software development solution provider . Visualization tool diagram ( such as Use Case diagram ) can be used as main reference for discussion between the stakeholders of any software development project .