Instructions
This session involves a short quiz that you can copy and paste from this screen and answer the questions. The second part is answering a short question.
Module Number 2- Information Gathering and Eliciting System Requirements
Multiple Choice Quiz
Highlight the best answer (answer by highlighting the correct answer in RED)
Highlight the best answer
1 – Which of the following should be represented on a Data Flow Diagram.
- Database
- Source
- Attribute
- Entity
- Process
2 – Entity Relationship Diagram focuses upon.
- Actors
- Data
- Entities
- Information
3 – Which of the following relates to enterprise interoperability.
- DFD
- ERD
- Context Diagrams
- Information Flow diagram
4 – A functional decomposition diagram is a ____ representation of a function process.
- Bottom-up
- Top-down
- Parallel
- Sideways
5 ___ Refers to the logical rules that are applied to transform the data into meaningful information.
- Inputs
- Outputs
- Processes
- Controls
6 ___ Are the necessary data that enter the system.
- Inputs
- Outputs
- Processes
- Controls
7 __ questions encourage spontaneous and uninstructed responses
- Closed-questions
- Open-questions
- Leading-questions
- Probing-questions
Observing a system in use at another location is called a (n) ____.
- Operational visit
- System visit
- Site visit
- Technical visit
aTrue/False
Instructions: Circle T if the statement is true or F if the statement is false.
8 – T F In an information system an entity is a person, place, thing, or event.
9 – T F Questionnaire methods stress intense interaction between system developers and users.
10 – T F Joint application development is tied to the SDLC development methodolog
Essay
Three Mistakes a Business Analyst Should Avoid
Introduction
Poor communication leads to confusion and misunderstanding. The persons to eliminate this problem in an organization are the Business Analyst (BA) (Hooks, 2016). BA is the intermediary body linking the IT department and the Business. The role of this group is to share information between the two stakeholders and clarify where we have ambiguity in the report.
Making Assumptions
Before a project launch, there are a lot of assumptions made. Lack of or limited knowledge about the project always triggers numerous assumptions. Lack of better communication between all the affected parties, especially in the management will bring about assumptions which most of the time are false. Treating these assumptions as fact is the problem. In a discussion involving stakeholders, assumptions are made, regulating the number of this assumptions is vital. A project manager should monitor his or her hypothesis. Well-articulated and documented view from the BA shades light to other members as well as preventing confusion.
Assumptions from other members should be limited. The BA should have proper communication skills when countering other people’s theories. Use of words like “I wonder” when dismissing an idea should not come up (Kendall & Kendall, 2014). Give chances to all stakeholders to give their contribution, listen to their thoughts and direct them accordingly where they go wrong. Ask them questions where they are not explicit enough. Assumption making stage is critical for the better outcome of the project.
Ignoring Stakeholders
Stakeholders who are challenging to deal with and those who are unapproachable sends away BA. Avoiding these people will not solve anything. If anything it creates more problems at the tail end. The thought of accommodating these people in decision-making process requires courage, and this should be dealt with immediately. In the meeting make sure all parties involved including those who are hard to reach. By so doing, all ideas are captured and incorporated in the final report.
When dismissing ideas, harsh words should not be used. Lovingly correct them and provide them with adequate time to defend their opinion as well. Those members who cannot be reached after all the means have been exhausted, contacting them through email should be the final step. Allowing them to contribute to the project will make them own it, and make them feel accommodated in issues affecting the organization.
Failing to Ask Questions
When nominating and recruiting members of the AB, their confidence should be put into test. Persons who are afraid of questioning ideas should not be offered such positions (Kendall, 2008). Some of the reason why people avoid question are; fear of looking dumb, lack of enough time, personal differences between the members and thought that “I should be knowing this already”.
All the above reason are baseless, for example claiming that you lack adequate time to address issues in a meeting. But having all the time to repeat processes over and over is somehow ironical. Therefore, before a meeting is adjourned issue ever need to be addressed and an agreement reached. All the proceeding of the conference should be documented for future reference.
References
Hooks, I. (2016). Three Mistakes a Business Analyst. REquirement Expert (TRAining and Services for Project Success), 4. Retrieved from http://reqexperts.com/resources/requirements-articles/articles-3-mistakes-a-ba-should-avoid/
Kendall, K. a. (2008). System Analysis and Design KEndall and KEndal fifth Edition. canada: 2008 pearson prentice hall.
Kendall, K., & Kendall, J. (2014). Systems analysis and design. Boston: Pearson.
Information Gathering and Eliciting System Requirements
SLP Overview
For this project, you will be briefly introduced to Data Flow Diagrams (DFD) and Entity Relationship diagrams (ERD) to depict the process analysis and data analysis paradigms.
Data Flow Diagrams (DFD) are used in structured analysis and design for process oriented systems such as legacy systems written in COBOL, C, or third generation languages. Process oriented was the first paradigm to model and diagram processes derived from interviews and system requirements. The SmartDraw tutorial has samples of DFD notations, layers, context, level, and nested diagrams. In structure analysis, the application context is designed first. Then, it follows a top-down approach to progressively more detailed levels until a process cannot be decomposed any longer. The application is documented through diagram forms as shown in the tutorial. Graphical representations replace some text on process descriptions. For this reason, notations are used.
The second paradigm is data oriented using Entity Relationship Diagrams (ERDs) to create the logical design for relational databases. You will need to review how notations and cardinality are integrated in the design. Data orientated analysis is based on the idea that data is more stable than processes since organizations always change the way they do functions. An ERD begins with defining entities such as a person with attributes related to first and last name, phone number, SSN, etc. The entities are then connected through cardinalities 1:1 (one to one), 1:M (one to many), and M:M (many to many) to interface to other entities. From a logical design perspective, database tables are created and normalized.
Modeling is an interactive process, and it is refined during walkthrough sessions with IT professionals and users. If you want more detail on inheritance and other forms, there are many diagrams examples on the Internet to freely view. Only the basics will be covered in Module 2.
SmartDraw. (2011). Software design tutorials. Retrieved from http://www.smartdraw.com/resources/tutorials/data-flow-diagrams/#/resources/tutorials/Introduction-to-DFD
The following examples introduce an inventory system illustrating how process modeling with DFDs and data modeling with ERDs are constructed.
CSUB. (n.d.). DFD example. Retrieved form http://www.sims.monash.edu.au/subjects/cse1204/assets/lecture07.pdf
Creatively Diagraming and Collaboration. (2012). Ultimate guide to ER diagrams. Retrieved from http://creately.com/blog/diagrams/er-diagrams-tutorial/
SLP Assignment
This session involves a short quiz that you can copy and paste from this screen and answer the questions. The second part is answering a short question.
Multiple Choice Quiz
Highlight the best answer (answer by highlighting the correct answer in RED)
Highlight the best answer
1 – Which of the following should be represented on a Data Flow Diagram.
- Database
- Source
- Attribute
- Entity
- Process
2 – Entity Relationship Diagram focuses upon.
- Actors
- Data
- Entities
- Information
3 – Which of the following relates to enterprise interoperability.
- DFD
- ERD
- Context Diagrams
- Information Flow diagram
4 – A functional decomposition diagram is a ____ representation of a function process.
- Bottom-up
- Top-down
- Parallel
- Sideways
5 ___ Refers to the logical rules that are applied to transform the data into meaningful information.
- Inputs
- Outputs
- Processes
- Controls
6 ___ Are the necessary data that enter the system.
- Inputs
- Outputs
- Processes
- Controls
7 __ questions encourage spontaneous and uninstructed responses
- Closed-questions
- Open-questions
- Leading-questions
- Probing-questions
Observing a system in use at another location is called a(n) ____.
- Operational visit
- System visit
- Site visit
- Technical visit
True/False
Instructions: Circle T if the statement is true or F if the statement is false.
8 – T F In an information system an entity is a person, place, thing, or event.
9 – T F Questionnaire methods stress intense interaction between system developers and users.
10 – T F Joint application development is tied to the SDLC development methodology.
Short Essay
Answer the following question in 500 words
What do you think are three most common mistakes that novice business analysts make in modeling process or data?
Assignment Expectations
Your paper will be evaluated on the following criteria:
- Complete the quiz and question. Copy the quiz in Word and highlight in red the correct answer. Follow with the 2-page essay (400 – 600 words) in the next page. Essay must be double spaced. Include a cover page with the assignment.
The essay will be graded on these requirements:
- Precision: the questions asked are answered.
- Clarity: Your answer to the short essay is clear and shows your good understanding of the topic.
- Breadth and Depth: The scope covered in your answer is directly related to the questions of the assignment and the learning objectives of the module.
- Critical thinking: Incorporate your reactions, examples, and applications of the material to business that illustrate your reflective judgment and good understanding of the concepts.
- Your short essay is well written, and the references are properly cited and listed.
Required Sources
PMPDQ. (2009, May 19). IT systems analyst: Plan the interview. [Video file]. Retrieve from http://www.youtube.com/watch?v=TMZWW3rkhtw
Kendall, K.E., & Kendall, J. E. (2011. Chapter 4 information gathering: Interactive methods. Systems Analysis and Design 8th ed. [PPT presentation]. Retrieved from Chapter 4 Information Gathering: Interactive Methods
Kuchmistaya, S. (2001). Incorporation of joint application design (JAD) in systems requirements determination. Retrieved from http://www.umsl.edu/~sauterv/analysis/488_f01_papers/kuchmistaya.htm
Dennis, A., Wixom, B. H., & Tegarden, D. (2008). Requirements determination. Systems Analysis and Design with UML 2.0. [PPT presentation]. Retrieved from http://www.computing.surrey.ac.uk/personal/st/J.Clark/teaching/sad/lectures/lec3.pdf
SmartDraw. (2011). Software design tutorials. Retrieved from http://www.smartdraw.com/resources/tutorials/data-flow-diagrams/#/resources/tutorials/Introduction-to-DFD
CSUB. (n.d.). DFD example. Retrieved form http://www.sims.monash.edu.au/subjects/cse1204/assets/lecture07.pdf
Creatively Diagraming and Collaboration. (2012). Ultimate guide to ER diagrams. Retrieved from http://creately.com/blog/diagrams/er-diagrams-tutorial/
Optional Material
Kendall, K. E., & Kendall, J. E. (2008). Chapter 6 using questionnaires. Systems Analysis and Design 5th ed. [PPT presentation]. Retrieved from www.mgt.ncu.edu.tw/~ylchen/sasd-slide/chap06.ppt