BOK-BOKs :: PMBOK, BABOK, SWEBOK & ...

Followng are few more points on the PMBOK (Project Management Body Of Knowledge, http://en.wikipedia.org/wiki/A_Guide_to_the_Project_Management_Body_of_Knowledge), BABOK (Business Analysis Body Of Knowledge, http://en.wikipedia.org/wiki/BABOK ), SWEBOK (Software Engineering Body of Knowledge, http://en.wikipedia.org/wiki/SWEBOK) ..

PMBOK:

A Guide to the Project Management Body of Knowledge — Fifth Edition provides guidelines for managing individual projects and defines project management related concepts. It also describes the project management life cycle and its related processes, as well as the project life cycle.

The Guide recognizes 47 processes that fall into five basic process groups and ten knowledge areas that are typical of almost all projects.

• The five process groups are:

1. Initiating
2. Planning
3. Executing
4. Monitoring and Controlling
5. Closing

• The ten knowledge areas are:

1. Project Integration Management
2. Project Scope Management
3. Project Time Management
4. Project Cost Management
5. Project Quality Management
6. Project Human Resource Management
7. Project Communications Management
8. Project Risk Management
9. Project Procurement Management
10. Project Stakeholders Management (added in 5th edition)

BABOK's 6 KAs (Knowledge Areas):

1. Business Analysis Planning and Monitoring,

2. Elicitation,

3. Requirements Management and Communication, 

4. Enterprise Analysis,

5. Requirements Analysis,

6. Solution Assessment and Validation

One can get the CBAP after about 5 years of experience in the Business Analysis roles:
http://en.wikipedia.org/wiki/Certified_Business_Analysis_Professional

SWEBOK's 10 KAs (Knowledge Areas):

• Software requirements
• Software design
• Software construction
• Software testing
• Software maintenance
• Software configuration management
• Software engineering management (Engineering management)
• Software engineering process
• Software engineering tools and methods
• Software quality

For the Software Requirements, You will need 6 TEAM Skills: (I'm copying the contnts I blogged here before ... :P ...)

----------------------------------------------------------------------------------------

1. Analyzing the Problem (AP)

2. Understanding User Needs (UUN)

3. Defining the System (DS)

4. Managing Scope (MS)

5. Refining the System Definition (RSD)

6. Building the Right System (BRS)

5 Generic Steps in Problem Analysis:

----------------------------------------------------

1. Gain understanding on the Problem Definition

2. Understand the Root Causes - the Problems behind the Problem

3. Identify the Stakeholders and Users

4. Define the Solution System Boundary

5. Identify the Constraints to be imposed on the Solution!

Few tips / advice for the aspiring Young Software Professionals:

--------------------------------------------------------------------------------------------

1. Be Passionate about the Software Development (genuinely...;-)...

2. Have an Agile Mindset in coping with the constant change in IT 

3. Invest in your early career rather than "running after money" (stop hopping...;-)

4. Find your own Mentors ... (or Be your own Mentor with Google & the Net...)

5. Have a Great "AIM" in Life ... (AIM => Assess / Accept your weaknesses / mistakes, Improve on those, and then Move on positively ...)

Few URLs for you to look at:

------------------------------------------

http://scratch.mit.edu/

http://brilliant.org/

http://rosalind.info/problems/locations/

http://www.codecademy.com/

http://www.mountaingoatsoftware.com/agile/user-stories

http://www.agiledata.org/essays/tdd.html

... And many more that you can find by "Googling" which might be more suited to your needs and interests ... :-) ...

Let's ALL enjoy the LEARNING ...:)