Beruflich Dokumente
Kultur Dokumente
Our goal is to create a clone of monster.com which is secure, fast, extensible and will scale
appropriately as the user base grows. We will achieve this goal while minimizing the required
effort by building on the team’s current skill set, utilizing off-the-shelve, open source
components where possible and making use of the Amazon AWS infrastructure and services as
much as possible.
The final product will be based around an open source Content Management System which we
will extend to meet our particular needs. The CMS should provide us with off the shelf tools and
services for user management, content management and publishing for static content like the
Advice section, Career Resources etc.
In order to optimize for parallelization of the development tasks while at the same time having
an integrated product from day one it is advised to use a framework or platform that is based
around the Model-View-Controller (MVC) pattern. This will provide the necessary separation of
concerns to allow for parallelization of development and testability we require.
Scope Metrics
Since we are making an exact copy of an existing site the most objective metric is the feature
parity between the original site and our own.
In the appendix at the end of the document we provide a breakdown of the “Upload Resume”
process in terms of Pages, Page Sections and Actions. These elements are very specific and
thus absolutely quantifiable.
What we call “page” is a design metaphor. It does not necessarily map to one and only one
URL. A page has a specific layout but may have different sections that are dynamic.
A “page section” is part of a page and represents a logical unit of information.
An “action” is a user initiated process the results in a new page section or a new page.
In this context, the “Upload Resume” Process consists of 5 pages and each page consists of a
different number of sections and actions as described in the Appendix.
An open source CMS that is based on ASP.NET MVC is Orchard. A Microsoft-backed, open
source CMS with a nice collection of off the shelf modules and large community support.
Since we are using Amazon AWS and assuming the team has some expertise with that, we
should take advantage of Amazon SimpleDB a no-sql database, adequate for our needs,
providing the availability and scalability features we need.
For BLOB file storage (for the uploaded resume files) we will have to use Amazon S3. Amazon
S3 meets our Security, Scalability and Performance requirements while keeping things simple.
Ideally, when tasks have been identified, the effort estimation for each task should be done by
the actual developers.
Calendar duration
Getting a commitment for the confidence point of 75%, utilizing 3 developers and 1 architect we
plan as follows
Units Breakdown
· Common Page artifacts
o Section: Header
o Section: Footer
· Page: My Resumes (http://my.monster.com/Resume/ManageResumes)
o Action: Add Resume
o Action: Copy Resume
o Action: Delete Resume
Note: If there are no resumes then the Create Resume page is displayed