Requirements Engineering

Despite popular belief, no two software solutions are born equal so why not allow yours to be created with due care and thorough practices from start to finish?

At Acmex, we have business analysts that discuss the project with client representatives. By using interviews, walkthroughs of user interface design, and prototype evaluations, we can see EXACTLY what you need from the solution. Typically, we’ll follow a process similar to that of below;

Scope Definition

Understanding the business vision, goals and objectives of the new or replaced solution; Defining the context for the project undertaking.

Analysis

Analyzing the elicited solution ideas, business, user, functionality data requirements, analyzing constraints, business rules, and solution quality attributes. Prototyping interfaces to provide visual models of the proposed solutions.

Validation

Prototyping requirements; Testing requirements; Negotiating, validating and verifying requirements with all stakeholders

Elicitation

Identifying requirements stakeholders eliciting requirements through interviews, workshops, focus groups, observations, document analysis, etc.

Documentation

Structuring and categorizing the requirements; Ensuring every individual business, user, functional, and nonfunctional requirement is complete, correct, feasible, concise, prioritized, unambiguous and verifiable.

Management

Managing requirements version control, change control, requirements status tracking and tracking; Enabling requirements reuse and risk management.

Requirements Specifications

At the first stage, we involve a Project Manager, Business Analyst, and a QA Engineer. With concise and adaptable documentation – with regards to use cases, vision and scope document, etc – we can provide all Acmex clients with the solid grounding for planning, design, and coding the project. In the finished specifications, you’ll see usability, security, performance, and any constraints planned in advance under a variety of different conditions and quantities.

Technical Design

As we progress to technical design, we add the input of the Software Architect to propose the best approach to meet the technical requirements of the project. As well as meeting these requirements, we find the balance so it also remains efficient and reliable in the long-term. By analyzing all the functional requirements, we pinpoint unfeasible ideas or those that would be inefficient to implement. From here, we can propose more efficient replacements.

UI/UX Mockups

Eventually, a UI/UX Expert will replace the Software Architect to test different interface ideas and explore the limits of what we can provide. In the UI mockups as well as the interactive wireframes, you’ll see the navigation structure, how the screen will be laid out in terms of color, controls, and graphics, and how the software will perform under certain conditions.

Working Prototype

Finally, we reach the ‘Proof-of-Concept’ stage and this is made up of smaller steps and create a functional prototype to see how accurately the requirements have been met. By utilizing various production tools, the prototypes develop until it's fully functional and able to take any necessary adjustment.

Flexible Engagement

From the beginning, we take all business requirements and attempt to create documented deliverables from each one.

Accurate Implementation

Provided by the customer, we assess all requirements before then translating these needs into high-quality software solutions.

Scope Creep Management

Of course, change happens sometimes so we also encourage proactive management at all times as the project goes from one stage to the next.

Have a project in mind?