5.1 Development Phase
The development phase illustrates the general strategy for building the system. It defines the objectives, goals, key components, tools, and dependencies necessary to ensure smooth execution. Internal and external dependencies, as well as required support, are carefully considered in this stage.
5.2 Development Objectives
Successful development depends on careful problem identification and systematic planning. Our strategy was built on strong design principles, ensuring that the code and applications generated meet user requirements.
-
Each requirement document was justified.
-
Every design phase was continuously reviewed.
-
The ultimate goal was to deliver a reliable product aligned with user expectations.
5.3 Overall Delivery Strategy
The final product passes through several small and large processes that are chained together according to standard practices.
-
Requirements and designs are translated into high-quality code.
-
The code undergoes multiple rounds of testing and debugging.
-
After refinement, the cleaned code is prepared for deployment.
5.4 Tradeoff Approach
Design and implementation were handled in separate phases with clearly defined sub-phases.
-
In the design phase, features were identified based on client needs and documented in specifications.
-
In the implementation phase, these features were developed synchronously because of their interconnected nature.
The order of development included features for user creation, user information, profiles, posting, commenting, liking, galleries, pages, and groups.
5.5 Key Design Goals
From an operational perspective:
-
Highest priority: user creation.
-
Next: user information and profile system.
-
Followed by: posts, galleries, comments, likes, pages, and groups.
From a security perspective:
-
Validate all forms to prevent injection attacks and session hijacking.
From a return-on-investment perspective:
-
Provide a platform for professionals of Khyber Pakhtunkhwa to exchange experiences and foster collaboration.
5.6 Development and Build Environment
The project was developed in a state-of-the-art lab environment using Microsoft technologies.
-
Documentation: Microsoft Word
-
Models: Microsoft Visio
-
Implementation: Microsoft Visual Studio
Core technologies used:
-
ASP.NET with C#
-
Microsoft SQL Server 2008
-
HTML5, CSS3, jQuery, and AJAX
Approach:
-
Build a template with HTML5, CSS3, and jQuery
-
Embed ASP.NET code into each section feature by feature
5.7 Guidelines and Standards
5.7.1 Coding Standards
-
Object-oriented approach
-
Camel casing for naming classes, methods, and objects
-
Avoid underscores and numbers for clarity and maintainability
Other standards:
-
3-Tier architecture applied for separation of concerns
-
Use of multiple databases where needed
-
Consistent page, form, and color design
5.8 Versioning and Source Control
-
Centralized source code management
-
Each feature was marked and integrated with its dependent modules after completion
5.9 Configuration and Development Management Tools
5.9.1 Microsoft Visual Studio 2012
Provided language support and tools for building ASP.NET applications with front-end technologies like HTML5, CSS3, jQuery, and AJAX.
5.9.2 Microsoft SQL Server 2008 R2
Used as the backend database for managing user data, posts, groups, and activities. It was selected due to its flexibility, ease of use, and speed.
5.10 Reuse
We adopted the 3-Tier architecture to promote code reuse.
-
A single block of code could serve multiple processes.
-
This improved efficiency, maintainability, and scalability.
Figures
-
Figure 5.1: Coding Environment
Shows the configuration of the IDE, coding tools, and development setup.
-
Figure 5.2: Global Connection Class
Illustrates the centralized database connection class that enabled all modules to communicate with the database efficiently.
Comments
Post a Comment