Process and Strategy

Initial Stages

• Project Scope

  1. Main ideas are discussed; to build a frame that will fit the picture, we ask questions, many of them are to get a high-level overview, about the project scope, business model, and targeted clients/audience; we learn your business so we can add to it.
  2. Pre-mature ideas are like babies, they need to be taken care of; Nilecode can help you to get it into action with that. Our business expertise will provide an advice and selective solutions that will put you on the right track and you are ready to go.
• Requirement Gathering

  1. Initial drafts were done after ensuring that scope of project is completely visible to Nilecode, we discuss project exact requirements and intended functionality.
  2. We are ready to map your requirements into technical ones, Nilecode will act as the man in the middle between your requirements, and the user needs, and monitoring that by using a pre-defined set of KPIs.
• Planning Ahead

  1. Learning how the project should move forward, by determining timeline, deliverables, and milestones. The agilability technique we use allows us to plan ahead and leave the door open for some specific components to be enhanced and integrated with more functions in the future.
• Resource Allocation

  1. Now that all items have been detailed, it is time to allocate needed resources to start working on the project.

Look and Feel & Concepts

• Wire Framing

  1. Is a process in which screens views are drawn in a rough manner to deliver the main concepts and explain how functionalities and actions are tied up together.
• Graphical Design

  1. In this process, project visual design is created based on the project scope and the client directions. Client will always be closely involved with the design team in this process to provide their directions.
• Prototyping

  1. A small version of the project with some basic functions will be delivered to interested clients so that they get their hands on a real experience of their project.

Development

• Task Prioritization

  1. Tasks are divided and prioritized so they could be assigned to developers.
• Product & sprint backlogs

  1. Product backlog contains the list of functionalities that should be implemented in the project. Sprint backlog contains the tasks that should be implemented in a certain work sprint.
• Sprints

  1. Following agile software development approaches, we work in sprints. A sprint is a work iteration in which a set of related functionalities are developed.
• Work Increments

  1. Work increments are the results of sprints. Each time a sprint is complete, we have a new work increment with the new functions added.

Quality Assurance and Testing

• Validation Testing

  1. Validates that the system is working and providing the exact functionality as dictated by the requirement specification documents.
• Functional & Verification Testing

  1. Performing a preliminary test of the system to assure that product conforms to Nilecode standards, to verify that we are building it the right way.
• Unit Testing

  1. Testing each unit in the system programmatically to ensure that it does the functionality it should provide.
• Compatibility Testing

  1. Testing the system to ensure backward compatibility, compatibility with web browsers and other used technologies.
• Stress Testing

  1. Putting a system in a continuous stress and heavy load for a certain period of time to make sure that it stands against any flood requests.
• Usability Testing

  1. Many persons are involved in usability testing to ensure that every part of the solution is usable to the most users.
• Penetration Testing

  1. Involves testing software to ensure that it is secure against any malicious attacks, threats, and vulnerabilities.

Delivery

After Delivery Support