Library

 

Name: Helper Utilities

Technology: .NET Framework Class Library

Summery:

Microsoft .NET Framework, a well designed software development platform, contain Base Class Library (BCL), to perform all required development task conveniently and efficiently. Since, this development framework was designed to capture a large area of software development requirements. The super set of BCL instances become a bit complex to use, especially when we have to consider a very common set of application requirements, ignoring other functionality and opportunities of the corresponding classes object model. Regarding his development experience in previous few years and the suggestions from the online developer community, he has developed a well engineered "Helper Library", which targets a common set of requirements and modeled in very simpler and reusable structure to fasten the development activities. This library includes, Simple Mailer, Simple Logger, Client Side Scripting Helper, Configuration Data Reader, Convenient Control Binder, Web Message Box, Query String Helper, Short String Dictionary, Excel Export, Simple HTML Builder, Simple Encryption utilities etc.

 

Templates

 

Templates are non-API development resources, which can't be re-used in binary (dll or exe) format. These are useful by coping to the source project and modifying as less as possible to fit the application requirements.

 

Documentation Template

 

Documentation is very important part of development. Regarding the requirement elicitation, analysis with end users, tracking the development progress, documentations for developers and end users should be well structured and defined to continue all type of documentation process perfectly. Ashraf maintains and guides his own set documentation structure and standard considering this issue.

 

Style Sheet Template

 

Style sheets are used to make the UI uniform among the whole application, by making the UI layout modification easier. Ashraf contains a Style Sheet Template that considers UI lay-outs regarding common application requirements.

 

UI and Content Template

 

Includes application header, footer, log-in, grid based, record based page UI templates, configuration file, commonly used images, testing templates.

 

Standards

 

Includes several development strategies along with describing the benefits for each of the options, by which the customer can pick the approach regarding their budget, time-line and application requirements. Besides, these standards help the software analysts, architects, designers, engineers, implementers, testers in a way that what are the options do they have that should keep in mind while working and thus implement the BEST approaches according to project requirements, budget etc.

 

01. Requirement Engineering

 

The current section provides a basic outline to discover, document requirement documents for a given software project. Some of the steps can be ignored if the application requirements are pretty simple or small. It includes research on application requirements, research on technical issues, application basic features, use cases, user interface specification, user requirements specification, application model, architecture, data fields, time estimation, UML notations etc.       

 

02. Database Analysis, Design and Implementation

 

Includes a basic definition out-lines for database related concepts and out-lines, like normalizations, functional dependencies etc.

 

03. User Interface Layouts

 

When we start a new project, there should be common conventions that should be followed on the following project. When this document will be sent to you, you may choose all of the options or edit any of the given option or can discard by simply deleting the corresponding standard. Remember many of the option include certain development cost, so consider ONLY the issues that are relevant, appropriate and very specific to your application requirements and budget.

 

These out-line includes the UI specifications like log-in page, site theme, date format, validator, control focus, grids, master-details pages, print pages, error pages, user manual etc.

 

04. Application Architecture

 

Design Goals: Concerns about the basic out-line for the design goals, like Correctness, Feasibility, Understandability, Modularity, Extensibility, Testability, Efficiency etc.

Ease of integration

 

Multilayer: Describes multi-layer architecture from several aspects.

 

05. Implementation

 

Includes a set of conventions, like UI control naming, syntax level naming, database object level naming etc.

 

06. Quality Assurance

 

Describes basic types of testing, QA goals.

 

07. Deployment

 

Describes a general out-line for efficient deployment and back-up scenarios.

 

08. Documentation

 

Basic categories of documents, benefits of documents, liabilities of documentation.