In the discipline of business analysis, the "hard skill" is writing (or modeling) and documenting the system or software requirements so that they are recorded, communicated and approved. Often, however, this important skill is also the one that is understood the least.

Various formats or deliverables are used to document system and software requirements. If you can understand them and how to combine them, you can produce a comprehensive set of requirements.

Author: David Wright

Comments

Currently, there are no comments. Be the first to post one!
You must be logged in to post a comment. You can login here

ARTICLE/PAPER CATEGORIES

» Activity Diagram
» Agile Methods
» Analytical and Problem Solving Skills
» Business Analysis Planning (BABOK KA)
» Business Process Management (BPM)
» Business Process Modeling Notation (BPMN)
» Career as a Business Systems Analyst
» CBAP
» Class Diagram
» Data Analysis & Modeling
» Elicitation (BABOK KA)
» Enterprise Analysis (BABOK KA)
» Estimation
» Functional Specifications
» Getting Started as a Business Systems Analyst
» IIBA & BABOK
» Interviewing & Hiring Business Systems Analysts
» Leadership & Management
» Process Improvement (CMMI, Six Sigma, SPICE, etc.)
» Project Management
» Requirements Analysis (BABOK KA)
» Requirements Management and Communication (BABOK KA)
» SDLC, Process, and Methodologies
» Security Analysis
» Service Oriented Architecture (SOA)
» Soft Skills
» Solution Assessment and Validation (BABOK KA)
» Structured Systems Analysis (DFDs, ERDs, etc.)
» Technical Topics
» Testing & Quality Assurance (QA)
» Tools
» Unified Modeling Language (UML)
» Use Cases
» User Interface & Usability
» Vertical Domain or Industry


Advertising Opportunities \| Contact Us

Privacy Statement | Terms Of Use