name report Posts

Step 1 of 2: Discovery

• PSDP Feasibility Phase: Setup legacy system for coders. Document legacy system using automated tools.
• PSDP Requirements Phase: Identify forms and reports to convert. Document terms, actors, and identify use cases. Identify enhancements (if any). Identify tables in use.
• PSDP Design Phase: Build new database. Initial screen design mockup. Document business rules and additional documentation of use cases.

Step 1 deliverables usually include a project plan for the Step 2 of 2 build-it phase which serves as the requirements, a new database, and a GUI mockup. Each form and report becomes a task in step 2 of our 2-step process along with other known tasks such as build data migration program, build MVC Shell Application, user subsystem, and admin forms for maintaining users, lookup tables, etc.

Step 1 of our 2 step approach is used to start a project with discovery. Step 2 is build. The goal of discovery is to document known requirements, some initial design, and a project plan. Step 1 of our 2 step includes at least the following tasks: Gather Requirements, Build GUI Mockup, and Create the Initial Database. The Requirements task becomes the project plan for step 2, Build.

Discovery can include additional tasks such as documenting an existing application, data cleanup, and even a task or two from the initial coding phase such as implementing our Prestwood ASP.Net MVC shell which includes some initial design, and member management.

If this ticket is not authorized, the printed version of the Project Plan is the Project Proposal for Discovery. Once authorized, the tasks of this project are completed. The requirements task is completed by creating a Step 2 of 2 project ticket which becomes the project plan and/or the proposal for Step 2, Build.

Define report specification and build. Integrate into reporting menu system.

Estimate Note: Most simple reports can be built in a half day, complex reports can take up to 16, very complex or redefined longer. 

Paradox for Windows has two primary file types: source files and delivered files. Source files in Paradox are binary but can can be opened in later versions of Paradox and even in earlier versions if you don't use any new features: .FSL = Form, .RSL = Report, .SSL = Script, and .LSL = Library. Since Paradox source files do not compile to an EXE, Paradox developers tend to use a startup form or script to start the application.