*Mail Me: [email protected]*
*Client Industry : Financial.* * * *Role : Sr Business Analyst * *Location : Beaverton, OR* * * *Duration : Long term* *Bill** Rate**: $35.00 CTC - Look for local candidates* * * *Start: Immediate* This is a business analyst position whose primary responsibility is to elicit, analyze, validate, specify, verify and manage the real needs of the project stakeholder, including customers and end users. This position will serve as a conduit between the business community and software development area through which requirements flow. This position will occasionally coordinate user acceptance testing (“UAT”) for projects they are associated with. ESSENTIAL FUNCTIONS: 1. Identify project stakeholders and user classes. Document user class characteristics. Identify appropriate representatives for each user class and negotiate their responsibilities. 2. Elicit requirements using interviews, document analysis, requirements workshops, storyboards, surveys, site visits, business process descriptions, use cases, scenarios, event lists, business analysis, competitive product analysis, task and workflow analysis, and/or viewpoints. 3. Write requirements specifications according to approved templates, using natural language simply, clearly, unambiguously, and concisely. 4. Decompose high-level business and user requirements into functional requirements and quality, specified in an appropriate level of detail suitable for use by those must base their work on the requirements. 5. Define quality attributes, external interfaces, constraints, and other nonfunctional requirements. 6. Represent requirements using alternative views, such as analysis models (diagrams), prototypes, or scenarios, where appropriate. 7. Lead requirements analysis and verification, ensuring that requirement statements are complete, consistent, concise, comprehensible, traceable, feasible, unambiguous, and verifiable, and that they conform to standards. 8. Participate in requirements prioritization. 9. Enter, manipulate, and report on requirements stored in a commercial requirements management tool. Define requirement attributes and facilitate their use throughout the project. 10. Manage requirements traceability information and track requirements status throughout the project. 11. Manage changes to baseline requirements through effective application of change control processes and tools. 12. Ensure that proposed system features and requirements meet user needs and satisfy business objectives and initiatives. 13. Develop requirement documentation that will translate business needs into requirements that can be understood by the application development team. 14. Design processes that support business initiatives 15. Perform and coordinate occasional User Acceptance testing as required on department related projects. 16. Develop procedures that maximize operational efficiencies while maintaining sound internal controls. *GENERAL SKILLS AND ABILITIES:* 1. Interviewing skills, to talk with individuals and groups about their needs and ask the right questions to surface essential requirements information 2. Listening skills, to understand what people say and to detect what they might be hesitant to say 3. Analytical skills, to critically evaluate the information gathered from multiple sources, reconcile conflicts, decompose high-level information into details, abstract up from low-level information to a more general understanding, distinguish presented user requests from the underlying true needs, and distinguish solution ideas from requirements 4. Facilitation skills, to lead requirements elicitation workshops 5. Observational skills, to validate data obtained via other techniques and expose new areas for elicitation 6. Writing skills, to communicate information effectively to customers, marketing, managers, and technical staff 7. Organizational skills, to work with the vast array of information gathered during elicitation and analysis and to cope with rapidly changing information 8. Interpersonal skills, to help negotiate priorities and to resolve conflicts among project stakeholders (such as customers, product management, and engineering) 9. Modeling skills, to represent requirements information in graphical forms that augment textual representations in natural language, including using modeling languages already established in the development organization 10. An understanding of contemporary requirements elicitation, analysis, specification, verification, and management practices and the ability to apply them in practice; familiarity with requirements engineering books and resources 11. An understanding of how to practice requirements engineering according to several software development life cycles in a team environment 12. Knowledge of product management concepts and how enterprise software products are positioned and developed 13. Application domain knowledge is a plus, to have credibility with user representatives and be able to work effectively with them *Andy* Resource Manager *West Coast Consulting* <http://www.westcoastllc.com/> 9233 Research Drive, Irvine, CA 92618, USA *Work:* 949-743-0065 Ext. 208 *Fax:* 714 844 9091 *Email:* [email protected] *IM:* andy_westcoastll (Yahoo) *Professional Profile* <http://www.linkedin.com/pub/4/2bb/917> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Oracle-USA" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Oracle-USA -~----------~----~----~----~------~----~------~--~---
