Expand All | Collapse All
- Overview
- Virtually all business services and products benefit from having a cutting-edge web presence to back them up. If your web presence is antiquted, slow, looks dated, or perhaps you don't have one, it's paramount that this area of your company look how you want your service or product to be viewed; as a sleek, streamlined, top-performing piece of work. This is where Christopher Ball, LLC comes into the picture.
- The basic business process, otherwise known as the software development life cycle (SDLC), involved in getting your site off the ground is as follows:
- First we meet and verbally go over what it is that your business does and what its needs are. We also discuss any project constraints you might have regarding time, budget, or technology.
- We then jointly put together a timeline of rough milestones to help keep things on some form of a schedule so that everyone has visilibilty into how the project will progress.
- The next step is critical and often requires the most attention, requirements definition, both at the high and detailed levels. Some clients prefer a more agile methodology where they like to sit down and refine requirements as things go through numerous iterations of development, while others prefer a more classic waterfall approach where more thought is spent up front focusing on the full set of needs before too much heavy lifting on the development side begins. In the end, there is no right choice and it all depends on the client and their preference.
- Now comes the development phase. Projects are typically developed from the back-end to the front-end. This means that a lot of the non-visual aspects, including database design and integration logic will be focused on first, followed by the user interface (UI) experience, and last but not least, all business related texts (copy) are then integrated into the UI.
- Then we arrive at the quality analysis (QA) phase. The goal is to locate and resolve any discovered bugs. Depending on the client, some prefer to utilize their own QA staff while others prefer it all be taken care for them, which is another viable option. Ultimately the desire is to have thoroughly tested all aspects of the website before customers start using it. As bugs are found and addressed, regression testing will be performed to ensure that not only the bugs are fixed but that no new bugs have been introduced in the process of doing so.
- After the final iteration of regression testing is complete, this is the client sign-off phase where you take a final look at the results and run it through any internal user acceptance testing (UAT) you might have planned. If any discoveries are made that warrant change, we cycle back through development and any necessary QA.
- At this point we work out all of the go-live details, including release notes, times and dates, parties involved and of course, rollback procedures if applicable.
- Once we arrive at launch day, your site now goes live and this is typically followed by close monitoring of system logs, traffic patterns and data in the database to ensure no major problems are going on behind the scenes.
- Leveraged Technologies
- Visual Studio 2010
- .NET 4 Framework
- MVC 3 Framework
- jQuery 1.7+
- JSON
- C#.NET
- ASP.NET
- LINQ
- AJAX
- Overview
- There are a number of different considerations to take into account when analyzing the security of a website. You might be asking yourself whether every website needs this level of analysis done, and the answer is yes, without question. If your site isn't protected adequately, a number of different kinds of risk factors exist, including defacement of your website, harm to your visitors, a breach of data or perhaps abuse of site functionality with unintended consequences.
- Primary Security Aspects Analyzed
- Cross Site Scripting (XSS)
- HTTP-POST data manipulation
- Sidejacking cookies
- Improper use or implementation of SSL certificates
- Improper storage of sensitive data
.NET Web Development