Skip to main content
Purdue Global
Information Technology
5 credits

Purdue Global IT391: Advanced Software Development

IT391 covers advanced design and programming concepts, applied across web and mobile contexts, with latitude in which language you implement assignments in. It sits late in the software development track and assumes you can already write working programs without hand-holding.

Fennie is independent and not affiliated with Purdue Global. This is an unofficial study guide.

What makes it hard

The freedom is the trap: choosing your implementation path means nobody hands you starter code, and debugging time is wildly unpredictable against fixed Tuesday deadlines. Students comfortable following tutorials struggle when assignments require designing a solution first, and a program that almost works the night it's due is worth very little.

What you'll cover

  • Advanced program design concepts
  • Object-oriented patterns in practice
  • Web application development
  • Mobile development concepts
  • Debugging and testing strategies
  • Cross-language programming principles

The IT391 study guide

How to study for Purdue Global IT391, step by step.

  1. 1

    Pick your language in week one and stay loyal

    IT391 lets you choose your implementation path. Pick the language you're strongest in and resist switching mid-term. The concepts transfer, but tool churn eats the hours the projects need.

  2. 2

    Start coding assignments the day the unit opens

    Debugging time is unpredictable, and a program that almost works on Tuesday night scores like a program that doesn't work. Early starts turn mystery bugs from disasters into Tuesday-morning fixes.

  3. 3

    Design before you type

    The assignments reward planned solutions: sketch the structure, the data flow, and the pieces before writing code. Tutorial-following habits break down here because nobody hands you the skeleton.

  4. 4

    Build a personal snippet library

    Keep working examples of the patterns the course uses (file handling, UI wiring, data structures) in one place. Reusing your own tested code is the difference between a 4-hour and a 10-hour assignment week.

  5. 5

    Test in slices, not at the end

    Run the program every time you add a piece. A bug introduced 20 minutes ago is findable; a bug somewhere in 300 new lines on deadline night is not.

Today

Today's IT391 plan

Preview
65 min

What a Fennie Daily Plan looks like for IT391. Yours is built from your own syllabus and adapts every day to your deadlines and progress.

0 / 4 done~65m remaining
Keep this plan free

First plan free, no card required. Fennie is independent and unaffiliated with your school.

FAQ

Is IT391 at Purdue Global hard?

It's one of the more demanding courses in the software track because assignments require designing and implementing solutions yourself, in your chosen language. Students who start early and test as they build manage it; deadline-night coders have a rough term.

What language is used in IT391?

The course emphasizes concepts that apply across languages and gives you a choice in implementation. Most students pick whichever language their earlier courses made them strongest in and stick with it all term.

How much programming experience do I need for IT391?

You should be able to write, run, and debug complete programs independently before starting. IT391 builds on earlier development courses and does not reteach fundamentals. Gaps there make every weekly project longer.

More Purdue Global courses