New Zealand's new Copyright Law presumes 'Guilt Upon Accusation' and will Cut Off Internet Connections without a trial. is against this unjust law - help us

A Space for All Things .NET Related

Exam 70-300 Objective 2

By James Hippolite, in , posted: 26-Mar-2009 14:56

Tested myself on Exam 70-300 (Analyzing Requirements and Defining Microsoft .NET Solution Architectures) Objective 2 (Gathering and Analyzing Business Requirements) and received only 46%.  I've got a bit of study to do, specifically:

  1. Gather and analyze business requirements
    • At the end of the planning phase, you complet ethe functional spec.
    • Current functionality; ID of business rule; Authority = busines rules catalog.
  2. Gather and analyze user requirements
    • User instruction; Surveys; Shadowing = user gathering info techniques
    • How about interruptions; can you resume?  What decision to start? = Typical questions
  3. Gather and analyze operational requirements
    • Behavioural view = the dynamic or changing state fo the system
    • Stabilizing phase = you identify, prioritize and resolve issues
  4. Gather and analyze requiremees for hardware, software, and network infrastructure
    • Develop wrong system, Define wrong reqs, Build wrong team, Budget over = risks of not creating functional spec

Other related posts:
Teach Yourself Azure in 4 hours
Geek Post Monthly Newsletter Volume 2 Issue 10

Add a comment

Please note: comments that are inappropriate or promotional in nature will be deleted. E-mail addresses are not displayed, but you must enter a valid e-mail address to confirm your comments.

Are you a registered Geekzone user? Login to have the fields below automatically filled in for you and to enable links in comments. If you have (or qualify to have) a Geekzone Blog then your comment will be automatically confirmed and shown in this blog post.

Your name:

Your e-mail:

Your webpage:

JamesHip's profile

James Hippolite
New Zealand

Welcome to my technical blog. 

Here, I attempt to distill the Microsoft Certified Professional Developer knowledge I have accumulated since first qualifying MCP in 1996.  This blog started on 13 September 2007 as an off-shoot from my mixed up personal blog.  But it took a shot in the arm from Scott Hanselman's talk at TechEd New Zealand 08 "32 Ways To Make Your Blog Suck Less".