Systems Analysis & Design class: please answer Questions #s 1-8 below: Describe
ID: 3915475 • Letter: S
Question
Systems Analysis & Design class:
please answer Questions #s 1-8 below:
Describe some of the challenges in using the basic system development life cycle. (You may use the experience your class team has had in working on their project:
Planning Phase:
1. As a Systems Analyst what approach would you take in identifying business needs for an organization?
2. What type of IT projects would make good use of your skills? Why?
3. What advice would you give new analysts who are inexperienced and beginning the planning phase of a new project? Give at least two pointers and explain why you think it is important for a rookie analyst to know.
Analysis Phase
4. Requirement Gathering
• Which one requirements elicitation technique are you most comfortable with to use? Why?
• Which one requirements elicitation technique seems least effective in your opinion? Why?
5. Use Cases
• What is your opinion on use cases?
• How might you make use cases work better?
6. Data Flow Diagrams
• What do you think are the three most difficult parts to understanding DFDs?
• What advice would you give a new student who is learning the DFD process?
7. Entity Relationship Diagrams
• The last element of the analysis phase describes the logical data analysis – creating an ERD. Why do you feel this is useful during the analysis phase?
8. What would be your approach in teaching future analysts about systems analysis and design?
Explanation / Answer
Q1) As a Systems Analyst what approach would you take in identifying business needs for an organization?
Capture Stakeholder Requirements - Ask each of these key stakeholders, or groups of stakeholders, for their requirements from the new product or service. What do they want and expect from this project?
Categorize Requirements - To make analysis easier, consider grouping the requirements into these four categories:
Interpret and Record Requirements - Once you have gathered and categorized all of the requirements, determine which requirements are achievable, and how the system or product can deliver them.
Q2) What type of IT projects would make good use of your skills? Why?
IT Management and Delievery Projects are best suited for my skill set because of my skills which are:-
Leadership - The issue of project leadership has always been and always will be a focal point among businesses. This is why it is undoubtedly at the top of a project manager most important skills. This skill enables project managers to come up with corporate visions and lead teams effectively.
Communication - Communication goes hand-in-hand with leadership skills. To be an effective leader, one has to be able to make clear what project teams must do. However, communication is not limited to the project team, it also applies to all stakeholders, including vendors, contractors and customers.
Contract Management - The ability to manage contracts is very useful in maintaining relationships with suppliers. As every project involves material supply, such skill really comes in handy for project managers. Managing purchases is basically the cream of contract management. As such functions have previously been handled by finance departments, relegating it to project managers makes the process much simpler.
Negotiating - Project managers who have excellent negotiating skills are likely to resolve conflicts that may arise among project stakeholders. This could lead to the formulation of ideal scenarios that could prove to be amicable to all concerned.
Team Management - Needless to say, most members of project teams need guidance from project managers and the most effective way to do this is by coaching. Having this skill will enable you to make up for employee shortcomings such as inadequate project experience and therefore, need coaching. And besides, coaching has been proven to help students to significantly boost their performance.
Task Management - An effective project manager should also be adept at task management. This skill involves the ability to come up with task lists and delegate them while keeping absolute control over the project. To be able to harness this skill, one must learn the process of making lists. Strategies for ensuring that one is constantly on top of such list should also be developed
Q3) What advice would you give new analysts who are inexperienced and beginning the planning phase of a new project? Give at least two pointers and explain why you think it is important for a rookie analyst to know.
Come to the job armed with a set of tools and techniques that you can readily transform into something of value to immediately show your stakeholders that they made the right decision when they chose you for the job. - The very first assignment should be done so well that it not only pleases your team leader but demonstrates to stakeholders that you possess the ability to clearly detail the business needs and value-added approaches to deriving a solution
Q4) Requirement Gathering
Which one requirements elicitation technique are you most comfortable with to use? Why?
Brainstorming
Benefit: You can avoid potential “gotchas” down the road by enlisting others to help you discover your unknowns. Also, more than most other methods, brainstorming enables you to take in a wide amount of information at once, helping you figure out where you want to go from here.
Done properly (without censoring ideas as you go) and with the right audience (representatives of each group, SMEs, stakeholders), brainstorming has the most potential to prevent gotchas down the road, capturing needs you didn’t know about, processes no one mentioned, and things you hadn’t thought of. To an extent, this takes the onus off you for knowing your unknowns by helping everyone think outside the box and helping stakeholders take ownership of the direction of a project. The myriad of ideas and information also give you a rich repository of knowledge to choose from, so you can discern where to go next with your project.
Which one requirements elicitation technique seems least effective in your opinion? Why?
Requirements Workshops - In a requirements workshop, you ask everyone to sit down and hammer out the requirements with you. “A requirements workshop is a highly productive focused event attended by carefully selected key stakeholders and subject matter experts for a short, intensive period (typically one or a few days).” To many analysts, this may sound impossible. Stakeholders are notorious for changing their minds and adding to discovery after six months—you’re going to put them in a conference room and nail down the scope over a weekend? To me its least effective as sometimes the indended audience attending are from totally different areas and the requirements are of no worth. This can furthur lead to wastage of time. Scheduling in weekends can lead to poor attendance, as nobody wants to attend Workshops in weekends.
Please let me know in case of any clarifications required. Thanks!
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.