Posted by mohamedr on January 3, 2012 – 10:48 am
This series of articles are addressed to IT persons who are not necessarily exposed to SharePoint. Those interested in Information Architecture (IA) and Enterprise Content Management would possibly find the subject more beneficiary than others. SharePoint specialists may be interested in the content from a high level and global perspective.
The objective of this series of articles is to examine SharePoint capabilities and limitations in the context of Enterprise Content Management, including Web Content Management.
In Part 1 I am going to discuss the notion of IA and its implications for Content Management Systems. Also, I will discuss the concept of SharePoint Governance and its relation to IA.
For the empirical purpose of this article I am going to adopt a very simple and clear definition of IA as:
“The organization of information into coherent structures that optimize its usefulness and enable its efficient navigation and retrieval (search). This usually requires the categorization of information using hierarchical or network artefacts.”
The above definition implies that developing an IA includes the following essential undertakings: Read More »
Yes, a rich internet based web application would be awesome, but is it really what you need? I would love to own a new Porsche 911, but not if I am using it to haul around building supplies for my construction company (unless it was balsa wood, maybe).
Just like using the right vehicle for the job, so should you be using the right software application for the right job. Here is an overview of the different application types that exist today, and some information about each to help you better understand your options when considering a new software application… Read More »
Systems are becoming more and more interconnected each day. Coordinating all that interconnectivity becomes a challenge, especially in terms of security. A party or client, such as a user, web service, web site, or even another device, may need to collaborate with more than one system. Using a claims-based security approach, a coordinated effort can be made to provide common security information to all systems . Here is how….
Read More »
There are actually methods to the madness in the process of gathering information for software requirements. As a system end-user or a subject matter expert it is likely that you have worked with others during some information gathering processes. Whether it was via a big meeting, or a simple phone call, someone probably has asked you a question or two about what you want the system to be or do. To help you better understand what is being asked of you, here is an overview of the two types of requirements that you are being asked about… Read More »
Building a new car requires the input of both a design team and an engineering team. Each team contributes to specific requirements. For example, the design team is responsible for understanding what the consumer wants in the look and feel of the car. The engineering team applies the required mechanics and functionality to the car. Both teams serve distinct purposes, however both teams need to eventually come together to produce what we will eventually drive down the road. Read More »
Let’s say you are a key system user or maybe a business subject matter expert. What would you typically tell someone when you explain what you do to accomplish a specific task? How about if you were to sit down train a new employee on a computer system. What information would you give to that new employee so that the employee can better learn how to do the job that needed to be done?
Just like training a new employee for a job, gathering information for software development projects requires a great deal of diligence. Not enough training, or giving a new employee the wrong information, could have a dramatic effect on how that new employee performs their tasks. Gathering the wrong requirements for a software project would have a dramatic effect on the delivery of a valid solution. Due diligence is required for software project requirements information gathering – making sure that the right solution is created for the right reasons. Read More »
Effectively communicating the same message to the many types of stakeholders in a software development project can be a challenge. Semantics used in a communication, such as that of a software requirement for example, can be received and interpreted differently from one person to the next. Often times each recipient will receive a communication however not everyone will have the same common understanding of what is being said.
There are many methodologies, models, and templates that attempt to provide a more cohesive understanding of a software solution design. The 4 + 1 View Model is one such way of describing a software system. Developed by Philippe Kruchten , currently a professor of software engineering at the University of British Columbia, the 4 + 1 View Model is a framework for presenting a consistent look at the design of a software system.
Read More »
Posted by robbie on August 5, 2011 – 11:54 am
NuGet is a recent extension to Visual Studio. For those of you familiar with Ruby’s gems, it allows you do the same thing – download, install and update libraries that are connected to its libraries, which makes working with third party libraries much easier.
In this post, I’ll go through how to install and use NuGet within the command prompt to get a third party component installed. In this example, we will install ELMAH, a set of error logging modules and handlers for ASP.NET. If your not familiar with ELMAH, I suggest you stay tuned into my future posts as I will be covering the benefits of using ELMAH in your projects.
The first step is to install NuGet. You can download a copy from http://nuget.org, the latest version is currently 1.4.
Read More »
