Systems Architect/Requirements Analyst

Description

GNTS Requirements process is very much a Use Case driven methodology. GNTS follows the Rational Unified Process (RUP) software development methodology consisting of standardized activities, artifacts, checklists, guidelines, tools and reviews sessions. The analyst must be able to understand the users' goals for the new system and then define the functional and quality requirements that allow project managers to estimate, developers to design and build, and testers to verify the product. Below are the typical tasks and skills required by an analyst to become effective at gathering and managing software requirements. This position also requires the requirements analyst to perform many tasks in the systems engineering arena. Systems engineering is concerned with the overall process of defining, developing, operating, maintaining, and ultimately replacing quality systems. Where other engineering disciplines concentrate on the details of individual aspects of a system (electronics, mechanics, aerodynamics, software, etc.), systems engineering is concerned with the integration of all of these aspects into a coherent and effective system. Systems engineers concentrate their efforts on the aspects of the engineering process (requirements definition, toplevel functional designs, project management, life cycle cost analysis,...) that serve to organize and coordinate other engineering activities. The systems engineer is the primary interface between management, customers, suppliers, and specialty engineers in the systems development process. RUP Methodology being familiar with Requirements Discipline usage of the standard set of requirements artifacts, activities & conceptsUML Modeling being familiar with standard set of System Models (e.g., Activity Diagrams, State Diagrams, Use Case Diagrams, etc.) to help analyze & validate requirementsRequirements Management Tool being familiar with System Tools to help mechanize the management & change control of requirementsUse Cases being familiar on how to develop and enforce good behavioral requirements through Use Case Specifications (requirements elicitation)