This page holds a finished IT-FPX4157 Assessment 1 requirements analysis, converting one organization's sites, users, applications and traffic into numbered requirements a design must satisfy. Searches like "it fpx 4157 assessment 1 assignment example", "itfpx4157 assessment 1 sample" and "it-fpx4157 assessment 1 example" land here.
What a finished IT-FPX4157 Assessment 1 requirements analysis looks like
The analysis reads as an interview written up, not as a design in disguise. It opens with the organization's geography: how many locations, how far apart, what sits at each one and who works there. User counts arrive by site and by shift, since a warehouse with forty scanners on one floor and a head office with forty desks make different demands. Applications appear next with what each needs from the network, whether steady bandwidth, low delay or nothing more than an occasional file. Traffic is described by direction, between sites, out to the internet, into a hosted service. Constraints are recorded exactly as the scenario states them: budget, existing cabling, a lease that ends, a link the organization cannot replace.
How a IT-FPX4157 Assessment 1 example is structured
The document moves from description to requirement and stops there. An environment section records what exists or is planned, site by site, with counts rather than adjectives: users, devices, floors, distances and whatever equipment the organization already owns. An application section follows, naming each system the business runs and what it asks of the network in terms a designer could size against. A traffic section describes the flows between those pieces, including the ones that cross between sites and the ones that leave for a hosted service. A constraints section collects the limits the scenario imposed and the assumptions made where it was silent, marked as assumptions. The requirements section then states each requirement in a numbered line, with the environment or constraint it came from cited beside it. A closing passage names the requirement the organization will find hardest to satisfy.
Counts recorded instead of adjectives
Users, devices, distances and floors appear as numbers, because a design cannot be sized against a site described as busy.
Applications stated as network demands
Each system the business runs is translated into what it asks of the network, so a later design has something to satisfy.
Every requirement cites its source
A numbered requirement names the sentence of the scenario it grew out of, so the whole list can be audited line by line.
Assumptions marked where the scenario is silent
Gaps are filled openly and labeled, since an unstated assumption becomes a design decision nobody can defend two assessments later.
No topology proposed yet
The analysis stops short of equipment and layout, because a requirements document written after the design explains nothing about either.
The hardest requirement named
A closing line identifies which requirement the organization's constraints make most difficult, which tells the next deliverable where the argument will be.
Where marks go in IT-FPX4157 Assessment 1
Requirements written after the design are the loss graders detect first, and they detect it by subtraction: choices appear in the later document that nothing in this list explains, or requirements appear here that exist only to justify equipment already chosen. Second is the description that never becomes a requirement, pages of scenario retold with no numbered line a design could be tested against. Third is the borrowed profile, bandwidth and latency figures imported from a general reference rather than derived from the applications the organization was described as running. Points also go for user counts recorded as ranges nobody can size against, for constraints the scenario stated but the analysis never records, and for assumptions made silently where the prompt said nothing. Distinguished analyses usually record the requirement they could not source and why.
Get a IT-FPX4157 Assessment 1 example written to your instructions
The scenario's counts are what the whole list hangs on, so send the Assessment 1 instructions, the scoring guide and the full site description your section uses. The requirements analysis returns inside 24 to 48 hours with each line traced to its source, and the first one is provided at no cost.
IT-FPX4157 Assessment 1 questions, answered
Can I include a topology sketch in the requirements document?
Check your instructions, because most sections keep the design for the next assessment and score this one on the written requirements alone. Where a sketch is allowed it should show what exists rather than what you propose, since a proposed layout here quietly turns the requirements into a justification for it. The marks in this deliverable sit in traceability, not in drawing.
How do I estimate traffic without measuring anything?
Derive it from the applications and the counts the scenario supplies, and put the arithmetic on the page. So many users running that system at once, each moving roughly this much, gives a figure a reviewer can check and argue with. Cite whatever published guidance you use for per-user demand. Numbers that arrive with no derivation are the ones a grader treats as invented.
How many requirements should the list contain?
As many as the scenario actually produces, each one testable. A requirement a design could satisfy or fail is worth counting; a sentence saying the network should be reliable is not, because no later document can be measured against it. Where your instructions set a format, follow it, and keep performance, capacity, availability and constraint requirements distinguishable from one another.