求知 文章 文库 Lib 视频 iPerson 课程 认证 咨询 工具 讲座 Modeler   Code  
会员   
 
  
 
 
 

需求分析-1-非功能性需求

 

2011-1-24 来源:网络

 

  Responsibilities

  · Elicit requirements using interviews, document analysis, requirements workshops, storyboards, surveys, use cases, scenarios, competitive product analysis, task and workflow analysis.
    · Document requirements, business processes (through use cases) and business rules in keeping with standard templates, using clear language: simple, explicit and concise.
    · Define external interfaces, constraints(pre/post), and other nonfunctional requirements.
    · Represent requirements using alternative views, such as analysis models or sketches, where appropriate.
    · Lead requirements analysis and verification, ensuring that requirement statements are complete, consistent and comprehensive.
    · Participate in requirements prioritization.
    · Participate in peer reviews of work products derived from requirements specifications to ensure that the requirements were interpreted correctly. Work hand-in-hand with Engineering during development to ensure requirements are understood.
    · Identify requirements errors and defects, and write requirements defect identification and notification reports.
    · Manage changes to baseline requirements through effective application of change control processes and tools.

  Qualifications

  · 5+ years experience in requirement analysis
    · Ability to interact professionally with a diverse group, executives, managers, and subject matter experts.
    · Strong listening and communication skills coupled with strong interviewing and questioning skills
    · Excellent writing and analytical skills
    · Solid command of the language and the ability to express complex ideas clearly.
    · Strong negotiation, organizational, and facilitation skills
    · A proven ability to find creative ways of satisfying user needs
    · Proficient in MS Word, Excel and PowerPoint skills.
    · Excellent modeling skills through structured analysis models (DFD, ERD, UML etc).
    · IT/Business background and industry experience is a strong plus.

  nonfunctional requirements

  General
    NFR-1 Do the requirements conform to CxCheck_Requirements?
    NFR-2 Are the requirements stated in a specific and     measurable form? (e.g. 10 sec vs. fast)
    Reliability
    NFR-3 Are the reliability (MTBF) requirements specified?
    NFR-4 Are the availability (up time) requirements specified?
    NFR-5 Are the serviceability (MTTR) requirements specified?
    NFR-6 Are the robustness requirements specified?
    Performance
    NFR-7 Are the response time or latency requirements specified?
    NFR-8 Are the throughput requirements specified?
    NFR-9 Are the data volume requirements specified? (input, stored, output)
    NFR-10 Are the peak or short-term load requirements specified?
    Hazard/Safety/Security
    NFR-11 Are the security requirements specified?
    NFR-12 Are the safety requirements specified?
    Configurations
    NFR-13 Are the supported configurations specified?
NFR-14 Are the compatibility requirements specified?     (backwards, other applications, etc.)
    Usability
    NFR-15 Are the usability requirements specified?
    NFR-16 Are the internationalization/localization requirements specified?
    NFR-17 Are the look and feel requirements specified? (e.g. color schemes, standards, etc.)
    Operational
    NFR-18 Are any operational constraints or requirements     specified? (e.g. the user must be able to
    operate the system using ski gloves)
    Specification Methods
    NFR-19 Does the specification conform to CxCheck_SoftwareRequirementsSpecification?

  Functional Requirements are MUST TO HAVE (The system will not function without these requirements);
Non-Functional Requirements are NICE TO HAVE (The system will work however, NFR will increase the usability or performance related issues.)

  Here are some key categories of non-functional requirements:
    1. GUI look and feel requirements
    2. Performance requirements
    3. Capacity requirements
    4. Security requirements
    5. Availability requirements
    6. Exception Handling requirements
    7. Logging requirements
    8. Extensibility requirements
    9. Data Retention requirements
etc.



需求分析方法—把测试流程图表化
敏捷需求分析五大关键因素
写好市场需求文档的10种技巧
需求分析中减少客户摩擦的法则
软件项目需求管理复杂性分析
EPC-事件驱动的流程链
更多...   


软件需求分析与管理实践
业务建模与业务分析
软件需求分析与管理
软件需求分析师
面向产品的需求分析与管理
IT规划体系与实践


北京 软件需求分析与管理
某知名基金 软件需求分析
联想 业务需求分析与建模
财税领域某IT服务商 测试需求分析
医疗行业 面向产品的需求管理
某知名IT服务商 测试需求分析>
某高新技术公司 测试架构、需求分析
更多...