BIS302 Web Application Development at Southern Cross Institute: Writing the Assessment 2 Website Requirements Plan
BIS302 Web Application Development at Southern Cross Institute (SCI) follows students through a two-part assessment structure, and Assessment 2 — the Website Requirements Plan — is where the business idea chosen in Assessment 1 has to become a genuine, technically justified web development plan. Worth 25% and testing ULO2 ("select and justify appropriate web technologies for a context or application using sound web engineering and design principles"), it's a 2,000-word individual report with a very specific six-part structure. Here's how to approach each part the way SCI's rubric rewards.
What Assessment 2 Actually Asks For
Assessment 2 builds directly on the business category and concept you selected in Assessment 1 — it isn't a fresh start, it's the technical follow-through. You're asked to produce a Website Requirements Plan covering six components: an executive summary, the website's objectives, a full user specification, structure charts, storyboards with rationale, and a conclusion and recommendation, backed by at least five peer-reviewed sources published within the last ten years and referenced in APA 7th. The brief is unusually specific about word allocation per section, which matters because SCI's markers are explicitly checking whether each section gets proportionate depth rather than being padded or rushed.
Why "Analysis" Beats "Description" on This Rubric
The rubric's heaviest-weighted criteria — Analysis of Web Technology Requirements (20%) and Structure Charts and Storyboards (20%) — both reward analytical depth over surface description. A report that lists web technologies without explaining why each one suits the specific business context will underperform even if the list is accurate. The same is true of Selection and Justification of Web Technologies (15%): naming a tech stack isn't enough, you need to justify each choice against the actual requirements of the business idea you're building for. Consideration of Future Trends and Futureproofing (15%) is the section most students under-develop — it specifically asks you to look beyond the immediate build and address how the site would scale, adapt to new devices or standards, or accommodate future features.
Breaking Down the Six Sections
1. Executive Summary (~150 words)
A tight overview of the business concept, the purpose of the website, and the key technology recommendations — written last, even though it appears first, so it accurately reflects the finished report.
2. Website Objectives (~250 words)
Clear, specific objectives that connect directly back to the business goals from Assessment 1 — not generic statements like "attract customers," but objectives tied to what this particular business needs the site to achieve (bookings, catalogue browsing, lead capture, community engagement).
3. User Specification (~650 words)
The largest section by word count, and it needs genuine user-centred thinking: who the site's users are, what devices and contexts they'll access it from, what functional and non-functional requirements follow from that (accessibility, load speed, mobile responsiveness, security), and how those requirements shape the technology decisions that follow.
4. Structure Charts (~300 words + diagrams)
A clear visual hierarchy of the site's pages and how they connect, paired with a written explanation of the logic behind the structure — why pages are grouped and linked the way they are, and how that structure supports the user journey.
5. Storyboards and Rationale (~500 words + visuals)
Visual mockups of key pages or user flows, each backed by a written rationale explaining the design and layout decisions. This is where the practical translation of the user specification into an actual interface happens, and it's marked jointly with the structure charts at 20% — the single heaviest-weighted section in the report.
6. Conclusion and Recommendation (~150 words)
A concise close that ties the plan back to the business objectives and makes a clear recommendation on the technology direction, rather than simply restating what's already been said.
Choosing and Justifying a Technology Stack
The strongest BIS302 submissions justify technology choices against three things at once: the specific functional requirements identified in the user specification, the scale and budget realities of the business idea from Assessment 1, and future flexibility. A content-heavy small business site and an interactive booking platform call for genuinely different stack decisions — a static site generator or lightweight CMS might suit one, while a framework with proper backend support suits the other. Naming a popular framework because it's popular, without connecting it to the actual requirements, is one of the most common ways marks are lost on the Selection and Justification criterion.
Common Mistakes in BIS302 Website Requirements Plans
- Disconnecting Assessment 2 from Assessment 1. The plan needs to visibly build on the business category and concept already chosen — a requirements plan for a generic, unrelated site scores poorly regardless of technical quality.
- Listing technologies instead of justifying them. Naming a stack without explaining why it fits the specific user requirements and business context caps the Selection and Justification and Analysis criteria.
- Skipping futureproofing. Consideration of Future Trends is a dedicated 15% criterion; a plan that only addresses present-day requirements leaves marks unclaimed.
- Weak structure charts or storyboards. These are marked jointly at 20% — the single largest share of the rubric — and need both clear visuals and a written rationale, not diagrams alone.
- Ignoring word allocation per section. SCI's brief specifies an approximate word count for each of the six sections; padding the executive summary while under-writing the user specification signals poor planning to markers.
- Under-referencing. At least five peer-reviewed sources published within the last ten years, in APA 7th, are required — general web content and outdated sources don't meet this bar.
Using GenAI Tools on This Assessment
Unlike some units that prohibit AI tools outright, BIS302's Assessment 2 brief explicitly permits generative AI for idea generation, structuring and drafting support — provided the output is critically reviewed, paraphrased into your own words, and properly referenced. SCI requires AI-assisted content to be cited in APA 7th using their specified ChatGPT/GenAI citation format where applicable. This makes BIS302 a good example of how AI policy varies genuinely by unit and by assessment, not just by institution — always check your specific assessment brief rather than assuming a blanket rule.
About Southern Cross Institute
Southern Cross Institute is a Parramatta-based higher education provider offering business and IT-focused qualifications, with BIS302 Web Application Development forming part of its applied information systems curriculum. The two-part Assessment 1/Assessment 2 structure is designed to take students from a business concept through to a technically justified website plan, mirroring how real web projects move from concept to requirements documentation before development begins. As always, confirm your specific due date and any lecturer clarifications on your unit's learning platform alongside general guidance like this.
How Punjab Assignment Help Supports BIS302 Students
We help Southern Cross Institute students with BIS302 assessments by:
- Helping you carry your Assessment 1 business concept through into a coherent, well-justified Assessment 2 requirements plan.
- Strengthening your technology justification so it's tied to genuine user requirements and business context, not just popular tool names.
- Reviewing your structure charts and storyboards for the clarity and rationale SCI's rubric rewards most heavily.
- Sourcing credible peer-reviewed references within the last ten years and checking APA 7th formatting and word allocation before submission.
Frequently Asked Questions
Does BIS302 Assessment 2 need to connect to Assessment 1?
Yes — the Website Requirements Plan is explicitly a continuation of the business category and concept chosen in Assessment 1, not a standalone exercise.
How long should the BIS302 Assessment 2 report be?
Approximately 2,000 words (±10%), split across six sections with specific word-count guidance for each, from a 150-word executive summary through to a 150-word conclusion.
Can I use ChatGPT or other GenAI tools for BIS302?
Yes, provided the assessment brief for your specific unit permits it — BIS302's Assessment 2 explicitly allows GenAI for idea generation and drafting support as long as output is critically reviewed, paraphrased, and referenced in APA 7th using SCI's specified citation format.
How many references does BIS302 Assessment 2 require?
At least five peer-reviewed sources published within the last ten years, referenced in APA 7th.
Can Punjab Assignment Help assist Southern Cross Institute students specifically?
Yes — we support SCI students with BIS302 and other web development and IT assessments, including technology justification, structure chart and storyboard development, and reference sourcing.