|
|
browse.develop.com
Browse.develop.com is a community that was established to collect and
organize valuable web information. Our technical staff have selected and
indexed information and courses that they feel will help you stay
current on best practices across the SDLC.
|
53 Articles match "Requirements"
|
Related DevelopMentor Courses
|
MORE
|
|
Essential Techniques for Gathering Requirements
Describe the planning, techniques, and partnerships that are vital to the success of requirements gathering Identify and differentiate between the different types of requirements that need to be gathered Describe the importance of documenting business objectives and project scope before gathering requirements Utilize a context diagram to scope the requirements Utilize a process, techniques, and templates for stakeholder identification and analysis Apply industry best practices to common issues with Stakeholders during requirements elicitation Plan and Conduct a Good Interview and a Facilitated
DevelopMentor Courses
- Friday, June 12, 2009
Essential LINQ with the Entity Framework
Day 2 LINQ to SQL: Introduction For years a problem known as the "object relational impedance mismatch" has stood as a barrier between the two worlds of objects and relational data, and in the past developers were responsible for writing the plumbing code required to go from one to the other. Through this mechanism, we can minimize the procedural code required for our applications. In this course, you learn to: Leverage new features of C# 3.0, including extension methods and lambda expressions Use LINQ to filter, sort, and group in-memory collections of objects Create LINQ to SQL
DevelopMentor Courses
- Friday, June 12, 2009
.NET Architecture and Design Principles: Building Distributed Applications
Think in terms of layers and tiers Use patterns in your code and across the enterprise Write secure code Use concurrency to build highly available systems Make distributed calls using remoting, web services and Windows Communication Framework Utilize asynchronous communication with message queues Horizontally scale every tier of your system Deploy software across distributed systems Applications that span more than one machine require a deliberate and radically different design approach. .NET NET architects, we transform high-level business requirements into a functional system within
DevelopMentor Courses
- Friday, June 12, 2009
|
197 Articles match "Requirements"
|
The Latest from DevelopMentor
|
MORE
|
|
|
|
-
|
The Best from DevelopMentor
|
MORE
|
-
Requirements, requirements everywhere; no clue on what to do
Twice this year I have visited companies which want to try a more Agile way of working but who have requirements coming of their ears. I’m talking hundreds of pages of requirements. Sometimes as big meat documents written by expensive consultants and bearing names like “Requirements Specification” or “Business Design.” Sometimes as use cases and scenarios. Its hard to argue with such requirements documents, in part because its hard to read them and understand what they are about.
Allan Kelly's Blog
- Friday, December 4, 2009
-
Managing requirements in Agile development
That is one of two reasons why Agile methods tend to underplay requirements and “Product Ownership” - because you get a lot of benefits by ignoring them to start with. The other is that Agile methods largely originated with developers who generally tend to underplay the role of requirements. (The But architects are also tasked with looking at technology therefore any requirements they come up with are likely I make no apologies for blogging again about Product Management because it is important and because, on the whole. As I said in my previous entry, Agile methods have
Allan Kelly's Blog
- Sunday, November 2, 2008
-
Requirements: The next challenge for Agile
Lets get one thing straight: I’m not saying requirements don’t matter. What I’m saying it: when the context is a broken development organization the most important thing is fixing the delivery process. In which case, you can, and should, take liberties with the requirements process. Then, when delivery shapes up you should come back and fix the requirements issues. Continuing my follow up to my latest tell of the Alignment Trap in the Agile Journal and on InfoQ . Because requirements is where the long term gain is.
Allan Kelly's Blog
- Monday, February 23, 2009
-
Systems Thinking: Requirements?
So how do you define requirement? The problem is that the notion of requirement comes in many forms. The definition seems to depend on what role you play in relationship to requirements definition – Customer, Business Analyst, Systems Analyst, Designer, Architect, [...]
...Tags: Tags: Systems Development Requirements System I was working with a large hospitality corporation when I was asked this question.
Jim Schardt's Blog
- Tuesday, January 6, 2009
-
Requirements and Black Boxes
After dealing with requirements in all sorts of shapes and sizes over the years I find the “black box” approach works well. For requirements, I think of any system as if it were a black box.
I Tags: Systems Development Black Box Requirements Systems Thinkin I can “see” or experience the outside of the box.
Jim Schardt's Blog
- Monday, January 12, 2009
-
More Black Box Requirements
In my last post I talked about how requirements are really the stuff that goes in and out of your system, the black box. But what else constitutes requirements (stuff)? Tags: Software Development Systems Development Black Box Business Rules QOS Requirement The “stuff” are things like data, documents, objects, requests, events, and when “this stuff happens. Well systems often adhere to rules.
Jim Schardt's Blog
- Tuesday, March 24, 2009
-
Avoiding Requirements Confusion with Black Boxes
By clearly understanding the boundary of your system you can easily distinguish between requirement and design statements.
...Tags: Tags: Software Development Black Box Requirements Systems Thinkin
Jim Schardt's Blog
- Monday, January 19, 2009
|
|
|
